Method by which multi-ru receives ldpc-tone-mapped ppdu in wireless lan system, and apparatus

ABSTRACT

Presented are a method by which a multi-RU receives a LDPC-tone-mapped PPDU in a wireless LAN system, and an apparatus. Particularly, a reception STA receives, from a transmission STA, a PPDU including a data field and decodes the data field. The data field is received through the multi-RU. LDPC tone mapping for data tone included in the data field is performed on the basis of a first parameter with respect to the multi-RU. The first parameter is 18 when the multi-RU is an RU in which the 242 tone RU and the 484 tone RU are aggregated.

BACKGROUND OF THE DISCLOSURE Field of the Disclosure

The present disclosure relates to a method for receiving data through a Multi-RU in a wireless LAN system and, more particularly, to a method and an apparatus for receiving a PPDU for which LDPC tone mapping has been performed in a Multi-RU.

Related Art

A wireless local area network (WLAN) has been improved in various ways. For example, the IEEE 802.11ax standard proposed an improved communication environment using orthogonal frequency division multiple access (OFDMA) and downlink multi-user multiple input multiple output (DL MU MIMO) techniques.

The present specification proposes a technical feature that can be utilized in a new communication standard. For example, the new communication standard may be an extreme high throughput (EHT) standard which is currently being discussed. The EHT standard may use an increased bandwidth, an enhanced PHY layer protocol data unit (PPDU) structure, an enhanced sequence, a hybrid automatic repeat request (HARQ) scheme, or the like, which is newly proposed. The EHT standard may be called the IEEE 802.11be standard.

In a new WLAN standard, an increased number of spatial streams may be used. In this case, in order to properly use the increased number of spatial streams, a signaling technique in the WLAN system may need to be improved.

SUMMARY

The present disclosure proposes a method and an apparatus for receiving a PPDU for which LDPC tone mapping has been performed in a Multi-RU in a wireless LAN system.

One embodiment of the present disclosure proposes a method for receiving a PPDU.

The present embodiment may be performed in a network supporting the next-generation wireless LAN system (the IEEE 802.11be or EHT wireless LAN system). The next-generation wireless LAN system is an improved version of the 802.11ax system and may satisfy backward compatibility with the 802.11ax system.

The present embodiment proposes a method for performing LDPC tone mapping on a data bit string included in the data field of a PPDU when transmitting the PPDU by allocating a Multi-RU supported by the 802.11be wireless LAN system to one STA. The Multi-RU refers to an RU in which several consecutive or inconsecutive RUs are aggregated.

A receiving station (STA) may perform the present embodiment and may correspond to an STA supporting an Extremely High Throughput (EHT) wireless LAN system. The transmitting STA of the present embodiment may correspond to an access point (AP).

A receiving STA receives a Physical Protocol Data Unit (PPDU) that includes a data field from a transmitting STA.

The receiving STA decodes the data field.

The data field is received through a Multiple-Resource Unit (Multi-RU). Low Density Parity Check (LDPC) tone mapping is performed on the data tone included in the data field for the Multi-RU based on a first parameter.

The Multi-RU may be allocated to the receiving STA (one STA) in a combination of various RUs. Also, the first parameter may be determined according to the number of data tones in the Multi-RU. The first parameter may correspond to D_(TM), which is an LDPC tone mapping distance parameter. The D_(TM) may be a tone interval used in LDPC tone mapping.

For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is 18. When the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4. When the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is 6.

Advantageous Effects

The embodiments of the present disclosure propose LDPC tone mapping parameters for Multi-RU to obtain an optimized data tone in terms of frequency diversity through LDPC tone mapping, thereby providing a new effect of increasing the overall throughput.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a transmitting apparatus and/or receiving apparatus of the present specification.

FIG. 2 is a conceptual view illustrating the structure of a wireless local area network (WLAN).

FIG. 3 illustrates a general link setup process.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20 MHz.

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

FIG. 8 illustrates a structure of an HE-SIG-B field.

FIG. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

FIG. 10 illustrates an operation based on UL-MU.

FIG. 11 illustrates an example of a trigger frame.

FIG. 12 illustrates an example of a common information field of a trigger frame.

FIG. 13 illustrates an example of a subfield included in a per user information field.

FIG. 14 describes a technical feature of the UORA scheme.

FIG. 15 illustrates an example of a channel used/supported/defined within a 2.4 GHz band.

FIG. 16 illustrates an example of a channel used/supported/defined within a 5 GHz band.

FIG. 17 illustrates an example of a channel used/supported/defined within a 6 GHz band.

FIG. 18 illustrates an example of a PPDU used in the present specification.

FIG. 19 shows an example of a PHY transmission procedure for HE SU PPDU.

FIG. 20 shows an example of a block diagram of a transmitting device for generating each field of an HE PPDU.

FIG. 21 shows an example of an LDPC tone mapping operation.

FIG. 22 shows an example of a DCM method being applied to data.

FIG. 23 shows an example of LDPC tone mapping having tone spacing set to 3 in a 52-tone RU in a situation where DCM is not applied.

FIG. 24 shows an example of LDPC tone mapping having tone spacing set to 3 in a 106-tone RU in a situation where DCM is applied.

FIG. 25 shows an example of LDPC tone mapping having tone spacing set to 18 in a 242+484 tone RU in a situation where DCM is not applied.

FIG. 26 shows an example of LDPC tone mapping having tone spacing set to 8 in a 2×484 tone RU in a situation where DCM is not applied.

FIG. 27 is a flow diagram illustrating the operation of a transmitting apparatus according to the present embodiment.

FIG. 28 is a flow diagram illustrating the operation of a receiving apparatus according to the present embodiment.

FIG. 29 is a flow diagram illustrating a procedure for a transmitting STA to transmit a PPDU according to the present embodiment.

FIG. 30 is a flow diagram illustrating a procedure for a receiving STA to receive a PPDU according to the present embodiment.

FIG. 31 illustrates an example of a modified transmitting device and/or receiving device of the present specification.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the present specification, “A or B” may mean “only A”, “only B” or “both A and B”. In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”.

A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”.

In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (EHT-signal)”, it may mean that “EHT-signal” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “EHT-signal”, and “EHT-signal” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., EHT-signal)”, it may also mean that “EHT-signal” is proposed as an example of the “control information”.

Technical features described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.

The following example of the present specification may be applied to various wireless communication systems. For example, the following example of the present specification may be applied to a wireless local area network (WLAN) system. For example, the present specification may be applied to the IEEE 802.11a/g/n/ac standard or the IEEE 802.11ax standard. In addition, the present specification may also be applied to the newly proposed EHT standard or IEEE 802.11be standard. In addition, the example of the present specification may also be applied to a new WLAN standard enhanced from the EHT standard or the IEEE 802.11be standard. In addition, the example of the present specification may be applied to a mobile communication system. For example, it may be applied to a mobile communication system based on long term evolution (LTE) depending on a 3rd generation partnership project (3GPP) standard and based on evolution of the LTE. In addition, the example of the present specification may be applied to a communication system of a 5G NR standard based on the 3GPP standard.

Hereinafter, in order to describe a technical feature of the present specification, a technical feature applicable to the present specification will be described.

FIG. 1 shows an example of a transmitting apparatus and/or receiving apparatus of the present specification.

In the example of FIG. 1, various technical features described below may be performed. FIG. 1 relates to at least one station (STA). For example, STAs 110 and 120 of the present specification may also be called in various terms such as a mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, or simply a user. The STAs 110 and 120 of the present specification may also be called in various terms such as a network, a base station, a node-B, an access point (AP), a repeater, a router, a relay, or the like. The STAs 110 and 120 of the present specification may also be referred to as various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, or the like.

For example, the STAs 110 and 120 may serve as an AP or a non-AP. That is, the STAs 110 and 120 of the present specification may serve as the AP and/or the non-AP.

STAs 110 and 120 of the present specification may support various communication standards together in addition to the IEEE 802.11 standard. For example, a communication standard (e.g., LTE, LTE-A, 5G NR standard) or the like based on the 3GPP standard may be supported. In addition, the STA of the present specification may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, or the like. In addition, the STA of the present specification may support communication for various communication services such as voice calls, video calls, data communication, and self-driving (autonomous-driving), or the like.

The STAs 110 and 120 of the present specification may include a medium access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for a radio medium.

The STAs 110 and 120 will be described below with reference to a sub-figure (a) of FIG. 1.

The first STA 110 may include a processor 111, a memory 112, and a transceiver 113. The illustrated process, memory, and transceiver may be implemented individually as separate chips, or at least two blocks/functions may be implemented through a single chip.

The transceiver 113 of the first STA performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be, etc.) may be transmitted/received.

For example, the first STA 110 may perform an operation intended by an AP. For example, the processor 111 of the AP may receive a signal through the transceiver 113, process a reception (RX) signal, generate a transmission (TX) signal, and provide control for signal transmission. The memory 112 of the AP may store a signal (e.g., RX signal) received through the transceiver 113, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, the second STA 120 may perform an operation intended by a non-AP STA. For example, a transceiver 123 of a non-AP performs a signal transmission/reception operation. Specifically, an IEEE 802.11 packet (e.g., IEEE 802.11a/b/g/n/ac/ax/be packet, etc.) may be transmitted/received.

For example, a processor 121 of the non-AP STA may receive a signal through the transceiver 123, process an RX signal, generate a TX signal, and provide control for signal transmission. A memory 122 of the non-AP STA may store a signal (e.g., RX signal) received through the transceiver 123, and may store a signal (e.g., TX signal) to be transmitted through the transceiver.

For example, an operation of a device indicated as an AP in the specification described below may be performed in the first STA 110 or the second STA 120. For example, if the first STA 110 is the AP, the operation of the device indicated as the AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 112 of the first STA 110. In addition, if the second STA 120 is the AP, the operation of the device indicated as the AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the AP or a TX/RX signal of the AP may be stored in the memory 122 of the second STA 120.

For example, in the specification described below, an operation of a device indicated as a non-AP (or user-STA) may be performed in the first STA 110 or the second STA 120. For example, if the second STA 120 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 121 of the second STA 120, and a related signal may be transmitted or received through the transceiver 123 controlled by the processor 121 of the second STA 120. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 122 of the second STA 120. For example, if the first STA 110 is the non-AP, the operation of the device indicated as the non-AP may be controlled by the processor 111 of the first STA 110, and a related signal may be transmitted or received through the transceiver 113 controlled by the processor 111 of the first STA 110. In addition, control information related to the operation of the non-AP or a TX/RX signal of the non-AP may be stored in the memory 112 of the first STA 110.

In the specification described below, a device called a (transmitting/receiving) STA, a first STA, a second STA, a STA1, a STA2, an AP, a first AP, a second AP, an AP1, an AP2, a (transmitting/receiving) terminal, a (transmitting/receiving) device, a (transmitting/receiving) apparatus, a network, or the like may imply the STAs 110 and 120 of FIG. 1. For example, a device indicated as, without a specific reference numeral, the (transmitting/receiving) STA, the first STA, the second STA, the STA1, the STA2, the AP, the first AP, the second AP, the AN, the AP2, the (transmitting/receiving) terminal, the (transmitting/receiving) device, the (transmitting/receiving) apparatus, the network, or the like may imply the STAs 110 and 120 of FIG. 1. For example, in the following example, an operation in which various STAs transmit/receive a signal (e.g., a PPDU) may be performed in the transceivers 113 and 123 of FIG. 1. In addition, in the following example, an operation in which various STAs generate a TX/RX signal or perform data processing and computation in advance for the TX/RX signal may be performed in the processors 111 and 121 of FIG. 1. For example, an example of an operation for generating the TX/RX signal or performing the data processing and computation in advance may include: 1) an operation of determining/obtaining/configuring/computing/decoding/encoding bit information of a sub-field (SIG, STF, LTF, Data) included in a PPDU; 2) an operation of determining/configuring/obtaining a time resource or frequency resource (e.g., a subcarrier resource) or the like used for the sub-field (SIG, STF, LTF, Data) included the PPDU; 3) an operation of determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) or the like used for the sub-field (SIG, STF, LTF, Data) field included in the PPDU; 4) a power control operation and/or power saving operation applied for the STA; and 5) an operation related to determining/obtaining/configuring/decoding/encoding or the like of an ACK signal. In addition, in the following example, a variety of information used by various STAs for determining/obtaining/configuring/computing/decoding/decoding a TX/RX signal (e.g., information related to a field/subfield/control field/parameter/power or the like) may be stored in the memories 112 and 122 of FIG. 1.

The aforementioned device/STA of the sub-figure (a) of FIG. 1 may be modified as shown in the sub-figure (b) of FIG. 1. Hereinafter, the STAs 110 and 120 of the present specification will be described based on the sub-figure (b) of FIG. 1.

For example, the transceivers 113 and 123 illustrated in the sub-figure (b) of FIG. 1 may perform the same function as the aforementioned transceiver illustrated in the sub-figure (a) of FIG. 1. For example, processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1 may include the processors 111 and 121 and the memories 112 and 122. The processors 111 and 121 and memories 112 and 122 illustrated in the sub-figure (b) of FIG. 1 may perform the same function as the aforementioned processors 111 and 121 and memories 112 and 122 illustrated in the sub-figure (a) of FIG. 1.

A mobile terminal, a wireless device, a wireless transmit/receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile subscriber unit, a user, a user STA, a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, a receiving unit, a transmitting unit, a receiving STA, a transmitting STA, a receiving device, a transmitting device, a receiving apparatus, and/or a transmitting apparatus, which are described below, may imply the STAs 110 and 120 illustrated in the sub-figure (a)/(b) of FIG. 1, or may imply the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1. That is, a technical feature of the present specification may be performed in the STAs 110 and 120 illustrated in the sub-figure (a)/(b) of FIG. 1, or may be performed only in the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1. For example, a technical feature in which the transmitting STA transmits a control signal may be understood as a technical feature in which a control signal generated in the processors 111 and 121 illustrated in the sub-figure (a)/(b) of FIG. 1 is transmitted through the transceivers 113 and 123 illustrated in the sub-figure (a)/(b) of FIG. 1. Alternatively, the technical feature in which the transmitting STA transmits the control signal may be understood as a technical feature in which the control signal to be transferred to the transceivers 113 and 123 is generated in the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1.

For example, a technical feature in which the receiving STA receives the control signal may be understood as a technical feature in which the control signal is received by means of the transceivers 113 and 123 illustrated in the sub-figure (a) of FIG. 1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers 113 and 123 illustrated in the sub-figure (a) of FIG. 1 is obtained by the processors 111 and 121 illustrated in the sub-figure (a) of FIG. 1. Alternatively, the technical feature in which the receiving STA receives the control signal may be understood as the technical feature in which the control signal received in the transceivers 113 and 123 illustrated in the sub-figure (b) of FIG. 1 is obtained by the processing chips 114 and 124 illustrated in the sub-figure (b) of FIG. 1.

Referring to the sub-figure (b) of FIG. 1, software codes 115 and 125 may be included in the memories 112 and 122. The software codes 115 and 126 may include instructions for controlling an operation of the processors 111 and 121. The software codes 115 and 125 may be included as various programming languages.

The processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, a logic circuit and/or a data processing device. The processor may be an application processor (AP). For example, the processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, the processors 111 and 121 or processing chips 114 and 124 of FIG. 1 may be SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or processors enhanced from these processors.

In the present specification, an uplink may imply a link for communication from a non-AP STA to an SP STA, and an uplink PPDU/packet/signal or the like may be transmitted through the uplink. In addition, in the present specification, a downlink may imply a link for communication from the AP STA to the non-AP STA, and a downlink PPDU/packet/signal or the like may be transmitted through the downlink.

FIG. 2 is a conceptual view illustrating the structure of a wireless local area network (WLAN).

An upper part of FIG. 2 illustrates the structure of an infrastructure basic service set (BSS) of institute of electrical and electronic engineers (i.e. EE) 802.11.

Referring the upper part of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs 200 and 205 (hereinafter, referred to as BSS). The BSSs 200 and 205 as a set of an AP and a STA such as an access point (AP) 225 and a station (STA1) 200-1 which are successfully synchronized to communicate with each other are not concepts indicating a specific region. The BSS 205 may include one or more STAs 205-1 and 205-2 which may be joined to one AP 230.

The BSS may include at least one STA, APs providing a distribution service, and a distribution system (DS) 210 connecting multiple APs.

The distribution system 210 may implement an extended service set (ESS) 240 extended by connecting the multiple BSSs 200 and 205. The ESS 240 may be used as a term indicating one network configured by connecting one or more APs 225 or 230 through the distribution system 210. The AP included in one ESS 240 may have the same service set identification (SSID).

A portal 220 may serve as a bridge which connects the wireless LAN network (i.e. EE 802.11) and another network (e.g., 802.X).

In the BSS illustrated in the upper part of FIG. 2, a network between the APs 225 and 230 and a network between the APs 225 and 230 and the STAs 200-1, 205-1, and 205-2 may be implemented. However, the network is configured even between the STAs without the APs 225 and 230 to perform communication. A network in which the communication is performed by configuring the network even between the STAs without the APs 225 and 230 is defined as an Ad-Hoc network or an independent basic service set (IBSS).

A lower part of FIG. 2 illustrates a conceptual view illustrating the IBSS.

Referring to the lower part of FIG. 2, the IBSS is a BSS that operates in an Ad-Hoc mode. Since the IBSS does not include the access point (AP), a centralized management entity that performs a management function at the center does not exist. That is, in the IBS S, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed by a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 may be constituted by movable STAs and are not permitted to access the DS to constitute a self-contained network.

FIG. 3 illustrates a general link setup process.

In S310, a STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, to access a network, the STA needs to discover a participating network. The STA needs to identify a compatible network before participating in a wireless network, and a process of identifying a network present in a particular area is referred to as scanning. Scanning methods include active scanning and passive scanning.

FIG. 3 illustrates a network discovery operation including an active scanning process. In active scanning, a STA performing scanning transmits a probe request frame and waits for a response to the probe request frame in order to identify which AP is present around while moving to channels. A responder transmits a probe response frame as a response to the probe request frame to the STA having transmitted the probe request frame. Here, the responder may be a STA that transmits the last beacon frame in a BSS of a channel being scanned. In the BSS, since an AP transmits a beacon frame, the AP is the responder. In an IBSS, since STAs in the IBSS transmit a beacon frame in turns, the responder is not fixed. For example, when the STA transmits a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA may store BSS-related information included in the received probe response frame, may move to the next channel (e.g., channel 2), and may perform scanning (e.g., transmits a probe request and receives a probe response via channel 2) by the same method.

Although not shown in FIG. 3, scanning may be performed by a passive scanning method. In passive scanning, a STA performing scanning may wait for a beacon frame while moving to channels. A beacon frame is one of management frames in IEEE 802.11 and is periodically transmitted to indicate the presence of a wireless network and to enable the STA performing scanning to find the wireless network and to participate in the wireless network. In a BSS, an AP serves to periodically transmit a beacon frame. In an IBSS, STAs in the IBSS transmit a beacon frame in turns. Upon receiving the beacon frame, the STA performing scanning stores information about a BSS included in the beacon frame and records beacon frame information in each channel while moving to another channel. The STA having received the beacon frame may store BSS-related information included in the received beacon frame, may move to the next channel, and may perform scanning in the next channel by the same method.

After discovering the network, the STA may perform an authentication process in S320. The authentication process may be referred to as a first authentication process to be clearly distinguished from the following security setup operation in S340. The authentication process in S320 may include a process in which the STA transmits an authentication request frame to the AP and the AP transmits an authentication response frame to the STA in response. The authentication frames used for an authentication request/response are management frames.

The authentication frames may include information about an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), and a finite cyclic group.

The STA may transmit the authentication request frame to the AP. The AP may determine whether to allow the authentication of the STA based on the information included in the received authentication request frame. The AP may provide the authentication processing result to the STA via the authentication response frame.

When the STA is successfully authenticated, the STA may perform an association process in S330. The association process includes a process in which the STA transmits an association request frame to the AP and the AP transmits an association response frame to the STA in response. The association request frame may include, for example, information about various capabilities, a beacon listen interval, a service set identifier (SSID), a supported rate, a supported channel, RSN, a mobility domain, a supported operating class, a traffic indication map (TIM) broadcast request, and an interworking service capability. The association response frame may include, for example, information about various capabilities, a status code, an association ID (AID), a supported rate, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise indicator (RSNI), a mobility domain, a timeout interval (association comeback time), an overlapping BSS scanning parameter, a TIM broadcast response, and a QoS map.

In S340, the STA may perform a security setup process. The security setup process in S340 may include a process of setting up a private key through four-way handshaking, for example, through an extensible authentication protocol over LAN (EAPOL) frame.

FIG. 4 illustrates an example of a PPDU used in an IEEE standard.

As illustrated, various types of PHY protocol data units (PPDUs) are used in IEEE a/g/n/ac standards. Specifically, an LTF and a STF include a training signal, a SIG-A and a SIG-B include control information for a receiving STA, and a data field includes user data corresponding to a PSDU (MAC PDU/aggregated MAC PDU).

FIG. 4 also includes an example of an HE PPDU according to IEEE 802.11ax. The HE PPDU according to FIG. 4 is an illustrative PPDU for multiple users. An HE-SIG-B may be included only in a PPDU for multiple users, and an HE-SIG-B may be omitted in a PPDU for a single user.

As illustrated in FIG. 4, the HE-PPDU for multiple users (MUs) may include a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy-signal (L-SIG), a high efficiency-signal A (HE-SIG A), a high efficiency-signal-B (HE-SIG B), a high efficiency-short training field (HE-STF), a high efficiency-long training field (HE-LTF), a data field (alternatively, an MAC payload), and a packet extension (PE) field. The respective fields may be transmitted for illustrated time periods (i.e., 4 or 8 μs).

Hereinafter, a resource unit (RU) used for a PPDU is described. An RU may include a plurality of subcarriers (or tones). An RU may be used to transmit a signal to a plurality of STAs according to OFDMA. Further, an RU may also be defined to transmit a signal to one STA. An RU may be used for an STF, an LTF, a data field, or the like.

FIG. 5 illustrates a layout of resource units (RUs) used in a band of 20 MHz.

As illustrated in FIG. 5, resource units (RUs) corresponding to different numbers of tones (i.e., subcarriers) may be used to form some fields of an HE-PPDU. For example, resources may be allocated in illustrated RUs for an HE-STF, an HE-LTF, and a data field.

As illustrated in the uppermost part of FIG. 5, a 26-unit (i.e., a unit corresponding to 26 tones) may be disposed. Six tones may be used for a guard band in the leftmost band of the 20 MHz band, and five tones may be used for a guard band in the rightmost band of the 20 MHz band. Further, seven DC tones may be inserted in a center band, that is, a DC band, and a 26-unit corresponding to 13 tones on each of the left and right sides of the DC band may be disposed. A 26-unit, a 52-unit, and a 106-unit may be allocated to other bands. Each unit may be allocated for a receiving STA, that is, a user.

The layout of the RUs in FIG. 5 may be used not only for multiple users (MUs) but also for a single user (SU), in which case one 242-unit may be used and three DC tones may be inserted as illustrated in the lowermost part of FIG. 5.

Although FIG. 5 proposes RUs having various sizes, that is, a 26-RU, a 52-RU, a 106-RU, and a 242-RU, specific sizes of RUs may be extended or increased. Therefore, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones).

FIG. 6 illustrates a layout of RUs used in a band of 40 MHz.

Similarly to FIG. 5 in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, and the like may be used in an example of FIG. 6. Further, five DC tones may be inserted in a center frequency, 12 tones may be used for a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 40 MHz band.

As illustrated in FIG. 6, when the layout of the RUs is used for a single user, a 484-RU may be used. The specific number of RUs may be changed similarly to FIG. 5.

FIG. 7 illustrates a layout of RUs used in a band of 80 MHz.

Similarly to FIG. 5 and FIG. 6 in which RUs having various sizes are used, a 26-RU, a 52-RU, a 106-RU, a 242-RU, a 484-RU, a 996-RU, and the like may be used in an example of FIG. 7. Further, seven DC tones may be inserted in the center frequency, 12 tones may be used for a guard band in the leftmost band of the 80 MHz band, and 11 tones may be used for a guard band in the rightmost band of the 80 MHz band. In addition, a 26-RU corresponding to 13 tones on each of the left and right sides of the DC band may be used.

As illustrated in FIG. 7, when the layout of the RUs is used for a single user, a 996-RU may be used, in which case five DC tones may be inserted.

The RU described in the present specification may be used in uplink (UL) communication and downlink (DL) communication. For example, when UL-MU communication which is solicited by a trigger frame is performed, a transmitting STA (e.g., an AP) may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA through the trigger frame, and may allocate a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. Thereafter, the first STA may transmit a first trigger-based PPDU based on the first RU, and the second STA may transmit a second trigger-based PPDU based on the second RU. The first/second trigger-based PPDU is transmitted to the AP at the same (or overlapped) time period.

For example, when a DL MU PPDU is configured, the transmitting STA (e.g., AP) may allocate the first RU (e.g., 26/52/106/242-RU. etc.) to the first STA, and may allocate the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit HE-STF, HE-LTF, and Data fields for the first STA through the first RU in one MU PPDU, and may transmit HE-STF, HE-LTF, and Data fields for the second STA through the second RU.

Information related to a layout of the RU may be signaled through HE-SIG-B.

FIG. 8 illustrates a structure of an HE-SIG-B field.

As illustrated, an HE-SIG-B field 810 includes a common field 820 and a user-specific field 830. The common field 820 may include information commonly applied to all users (i.e., user STAs) which receive SIG-B. The user-specific field 830 may be called a user-specific control field. When the SIG-B is transferred to a plurality of users, the user-specific field 830 may be applied only any one of the plurality of users.

As illustrated in FIG. 8, the common field 820 and the user-specific field 830 may be separately encoded.

The common field 820 may include RU allocation information of N*8 bits. For example, the RU allocation information may include information related to a location of an RU. For example, when a 20 MHz channel is used as shown in FIG. 5, the RU allocation information may include information related to a specific frequency band to which a specific RU (26-RU/52-RU/106-RU) is arranged.

An example of a case in which the RU allocation information consists of 8 bits is as follows.

TABLE 1 RU Allocation subfield (B7 B6 B5 B4 Number of B3 B2 B1 B0) #1 #2 #3 #4 #5 #6 #7 #8 #9 entries 00000000 26 26 26 26 26 26 26 26 26 1 00000001 26 26 26 26 26 26 26 52 1 00000010 26 26 26 26 26 52 26 26 1 00000011 26 26 26 26 26 52 52 1 00000100 26 26 52 26 26 26 26 26 1 00000101 26 26 52 26 26 26 52 1 00000110 26 26 52 26 52 26 26 1 00000111 26 26 52 26 52 52 1 00001000 52 26 26 26 26 26 26 26 1 00001001 52 26 26 26 26 26 52 1 00001010 52 26 26 26 52 26 26 1

As shown the example of FIG. 5, up to nine 26-RUs may be allocated to the 20 MHz channel. When the RU allocation information of the common field 820 is set to “00000000” as shown in Table 1, the nine 26-RUs may be allocated to a corresponding channel (i.e., 20 MHz). In addition, when the RU allocation information of the common field 820 is set to “00000001” as shown in Table 1, seven 26-RUs and one 52-RU are arranged in a corresponding channel. That is, in the example of FIG. 5, the 52-RU may be allocated to the rightmost side, and the seven 26-RUs may be allocated to the left thereof.

The example of Table 1 shows only some of RU locations capable of displaying the RU allocation information.

For example, the RU allocation information may include an example of Table 2 below.

TABLE 2 8 bits indices (B7 B6 B5 B4 Number of B3 B2 B1 B0) #1 #2 #3 #4 #5 #6 #7 #8 #9 entries 01000y₂y₁y₀ 106 26 26 26 26 26 8 01001y₂y₁y₀ 106 26 26 26 52 8

“01000y2y1y0” relates to an example in which a 106-RU is allocated to the leftmost side of the 20 MHz channel, and five 26-RUs are allocated to the right side thereof. In this case, a plurality of STAs (e.g., user-STAs) may be allocated to the 106-RU, based on a MU-MIMO scheme. Specifically, up to 8 STAs (e.g., user-STAs) may be allocated to the 106-RU, and the number of STAs (e.g., user-STAs) allocated to the 106-RU is determined based on 3-bit information (y2y1y0). For example, when the 3-bit information (y2y1y0) is set to N, the number of STAs (e.g., user-STAs) allocated to the 106-RU based on the MU-MIMO scheme may be N+1.

In general, a plurality of STAs (e.g., user STAs) different from each other may be allocated to a plurality of RUs. However, the plurality of STAs (e.g., user STAs) may be allocated to one or more RUs having at least a specific size (e.g., 106 subcarriers), based on the MU-MIMO scheme.

As shown in FIG. 8, the user-specific field 830 may include a plurality of user fields. As described above, the number of STAs (e.g., user STAs) allocated to a specific channel may be determined based on the RU allocation information of the common field 820. For example, when the RU allocation information of the common field 820 is “00000000”, one user STA may be allocated to each of nine 26-RUs (e.g., nine user STAs may be allocated). That is, up to 9 user STAs may be allocated to a specific channel through an OFDMA scheme. In other words, up to 9 user STAs may be allocated to a specific channel through a non-MU-MIMO scheme.

For example, when RU allocation is set to “01000y2y1y0”, a plurality of STAs may be allocated to the 106-RU arranged at the leftmost side through the MU-MIMO scheme, and five user STAs may be allocated to five 26-RUs arranged to the right side thereof through the non-MU MIMO scheme. This case is specified through an example of FIG. 9.

FIG. 9 illustrates an example in which a plurality of user STAs are allocated to the same RU through a MU-MIMO scheme.

For example, when RU allocation is set to “01000010” as shown in FIG. 9, a 106-RU may be allocated to the leftmost side of a specific channel, and five 26-RUs may be allocated to the right side thereof. In addition, three user STAs may be allocated to the 106-RU through the MU-MIMO scheme. As a result, since eight user STAs are allocated, the user-specific field 830 of HE-SIG-B may include eight user fields.

The eight user fields may be expressed in the order shown in FIG. 9. In addition, as shown in FIG. 8, two user fields may be implemented with one user block field.

The user fields shown in FIG. 8 and FIG. 9 may be configured based on two formats. That is, a user field related to a MU-MIMO scheme may be configured in a first format, and a user field related to a non-MIMO scheme may be configured in a second format. Referring to the example of FIG. 9, a user field 1 to a user field 3 may be based on the first format, and a user field 4 to a user field 8 may be based on the second format. The first format or the second format may include bit information of the same length (e.g., 21 bits).

Each user field may have the same size (e.g., 21 bits). For example, the user field of the first format (the first of the MU-MIMO scheme) may be configured as follows.

For example, a first bit (i.e., B0-B10) in the user field (i.e., 21 bits) may include identification information (e.g., STA-ID, partial AID, etc.) of a user STA to which a corresponding user field is allocated. In addition, a second bit (i.e., B11-B14) in the user field (i.e., 21 bits) may include information related to a spatial configuration. Specifically, an example of the second bit (i.e., B11-B14) may be as shown in Table 3 and Table 4 below.

TABLE 3 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) Total Number of N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8] N_(STS) entries 2 0000-0011 1-4 1 2-5 10 0100-0110 2-4 2 4-6 0111-1000 3-4 3 6-7 1001 4 4 8 3 0000-0011 1-4 1 1 3-6 13 0100-0110 2-4 2 1 5-7 0111-1000 3-4 3 1 7-8 1001-1011 2-4 2 2 6-8 1100 3 3 2 8 4 0000-0011 1-4 1 1 1 4-7 11 0100-0110 2-4 2 1 1 6-8 0111 3 3 1 1 8 1000-1001 2-3 2 2 1 7-8 1010 2 2 2 2 8

TABLE 4 N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) N_(STS) Total Number of N_(user) B3 . . . B0 [1] [2] [3] [4] [5] [6] [7] [8] N_(STS) entries 5 0000-0011 1-4 1 1 1 1 5-8 7 0100-0101 2-3 2 1 1 1 7-8 0110 2 2 2 1 1 8 6 0000-0010 1-3 1 1 1 1 1 6-8 4 0011 2 2 1 1 1 1 8 7 0000-0001 1-2 1 1 1 1 1 1 7-8 2 8 0000 1 1 1 1 1 1 1 1 8 1

As shown in Table 3 and/or Table 4, the second bit (e.g., B11-B14) may include information related to the number of spatial streams allocated to the plurality of user STAs which are allocated based on the MU-MIMO scheme. For example, when three user STAs are allocated to the 106-RU based on the MU-MIMO scheme as shown in FIG. 9, N user is set to “3”. Therefore, values of N_STS[1], N_STS[2], and N_STS[3] may be determined as shown in Table 3. For example, when a value of the second bit (B11-B14) is “0011”, it may be set to N_STS[1]=4, N_STS[2]=1, N_STS[3]=1. That is, in the example of FIG. 9, four spatial streams may be allocated to the user field 1, one spatial stream may be allocated to the user field 1, and one spatial stream may be allocated to the user field 3.

As shown in the example of Table 3 and/or Table 4, information (i.e., the second bit, B11-B14) related to the number of spatial streams for the user STA may consist of 4 bits. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to eight spatial streams. In addition, the information (i.e., the second bit, B11-B14) on the number of spatial streams for the user STA may support up to four spatial streams for one user STA.

In addition, a third bit (i.e., B15-18) in the user field (i.e., 21 bits) may include modulation and coding scheme (MCS) information. The MCS information may be applied to a data field in a PPDU including corresponding SIG-B.

An MCS, MCS information, an MCS index, an MCS field, or the like used in the present specification may be indicated by an index value. For example, the MCS information may be indicated by an index 0 to an index 11. The MCS information may include information related to a constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information related to a coding rate (e.g., 1/2, 2/3, 3/4, 5/6e, etc.). Information related to a channel coding type (e.g., LCC or LDPC) may be excluded in the MCS information.

In addition, a fourth bit (i.e., B19) in the user field (i.e., 21 bits) may be a reserved field.

In addition, a fifth bit (i.e., B20) in the user field (i.e., 21 bits) may include information related to a coding type (e.g., BCC or LDPC). That is, the fifth bit (i.e., B20) may include information related to a type (e.g., BCC or LDPC) of channel coding applied to the data field in the PPDU including the corresponding SIG-B.

The aforementioned example relates to the user field of the first format (the format of the MU-MIMO scheme). An example of the user field of the second format (the format of the non-MU-MIMO scheme) is as follows.

A first bit (e.g., B0-B10) in the user field of the second format may include identification information of a user STA. In addition, a second bit (e.g., B11-B13) in the user field of the second format may include information related to the number of spatial streams applied to a corresponding RU. In addition, a third bit (e.g., B14) in the user field of the second format may include information related to whether a beamforming steering matrix is applied. A fourth bit (e.g., B15-B18) in the user field of the second format may include modulation and coding scheme (MCS) information. In addition, a fifth bit (e.g., B19) in the user field of the second format may include information related to whether dual carrier modulation (DCM) is applied. In addition, a sixth bit (i.e., B20) in the user field of the second format may include information related to a coding type (e.g., BCC or LDPC).

FIG. 10 illustrates an operation based on UL-MU. As illustrated, a transmitting STA (e.g., an AP) may perform channel access through contending (e.g., a backoff operation), and may transmit a trigger frame 1030. That is, the transmitting STA may transmit a PPDU including the trigger frame 1030. Upon receiving the PPDU including the trigger frame, a trigger-based (TB) PPDU is transmitted after a delay corresponding to SIFS.

TB PPDUs 1041 and 1042 may be transmitted at the same time period, and may be transmitted from a plurality of STAs (e.g., user STAs) having AIDs indicated in the trigger frame 1030. An ACK frame 1050 for the TB PPDU may be implemented in various forms.

A specific feature of the trigger frame is described with reference to FIG. 11 to FIG. 13. Even if UL-MU communication is used, an orthogonal frequency division multiple access (OFDMA) scheme or a MU MIMO scheme may be used, and the OFDMA and MU-MIMO schemes may be simultaneously used.

FIG. 11 illustrates an example of a trigger frame. The trigger frame of FIG. 11 allocates a resource for uplink multiple-user (MU) transmission, and may be transmitted, for example, from an AP. The trigger frame may be configured of a MAC frame, and may be included in a PPDU.

Each field shown in FIG. 11 may be partially omitted, and another field may be added. In addition, a length of each field may be changed to be different from that shown in the figure.

A frame control field 1110 of FIG. 11 may include information related to a MAC protocol version and extra additional control information. A duration field 1120 may include time information for NAV configuration or information related to an identifier (e.g., AID) of a STA.

In addition, an RA field 1130 may include address information of a receiving STA of a corresponding trigger frame, and may be optionally omitted. A TA field 1140 may include address information of a STA (e.g., an AP) which transmits the corresponding trigger frame. A common information field 1150 includes common control information applied to the receiving STA which receives the corresponding trigger frame. For example, a field indicating a length of an L-SIG field of an uplink PPDU transmitted in response to the corresponding trigger frame or information for controlling content of a SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU transmitted in response to the corresponding trigger frame may be included. In addition, as common control information, information related to a length of a CP of the uplink PPDU transmitted in response to the corresponding trigger frame or information related to a length of an LTF field may be included.

In addition, per user information fields 1160#1 to 1160#N corresponding to the number of receiving STAs which receive the trigger frame of FIG. 11 are preferably included. The per user information field may also be called an “allocation field”.

In addition, the trigger frame of FIG. 11 may include a padding field 1170 and a frame check sequence field 1180.

Each of the per user information fields 1160#1 to 1160#N shown in FIG. 11 may include a plurality of subfields.

FIG. 12 illustrates an example of a common information field of a trigger frame. A subfield of FIG. 12 may be partially omitted, and an extra subfield may be added. In addition, a length of each subfield illustrated may be changed.

A length field 1210 illustrated has the same value as a length field of an L-SIG field of an uplink PPDU transmitted in response to a corresponding trigger frame, and a length field of the L-SIG field of the uplink PPDU indicates a length of the uplink PPDU. As a result, the length field 1210 of the trigger frame may be used to indicate the length of the corresponding uplink PPDU.

In addition, a cascade identifier field 1220 indicates whether a cascade operation is performed. The cascade operation implies that downlink MU transmission and uplink MU transmission are performed together in the same TXOP. That is, it implies that downlink MU transmission is performed and thereafter uplink MU transmission is performed after a pre-set time (e.g., SIFS). During the cascade operation, only one transmitting device (e.g., AP) may perform downlink communication, and a plurality of transmitting devices (e.g., non-APs) may perform uplink communication.

A CS request field 1230 indicates whether a wireless medium state or a NAV or the like is necessarily considered in a situation where a receiving device which has received a corresponding trigger frame transmits a corresponding uplink PPDU.

An HE-SIG-A information field 1240 may include information for controlling content of a SIG-A field (i.e., HE-SIG-A field) of the uplink PPDU in response to the corresponding trigger frame.

A CP and LTF type field 1250 may include information related to a CP length and LTF length of the uplink PPDU transmitted in response to the corresponding trigger frame. A trigger type field 1260 may indicate a purpose of using the corresponding trigger frame, for example, typical triggering, triggering for beamforming, a request for block ACK/NACK, or the like.

It may be assumed that the trigger type field 1260 of the trigger frame in the present specification indicates a trigger frame of a basic type for typical triggering. For example, the trigger frame of the basic type may be referred to as a basic trigger frame.

FIG. 13 illustrates an example of a subfield included in a per user information field. A user information field 1300 of FIG. 13 may be understood as any one of the per user information fields 1160#1 to 1160#N mentioned above with reference to FIG. 11. A subfield included in the user information field 1300 of FIG. 13 may be partially omitted, and an extra subfield may be added. In addition, a length of each subfield illustrated may be changed.

A user identifier field 1310 of FIG. 13 indicates an identifier of a STA (i.e., receiving STA) corresponding to per user information. An example of the identifier may be the entirety or part of an association identifier (AID) value of the receiving STA.

In addition, an RU allocation field 1320 may be included. That is, when the receiving STA identified through the user identifier field 1310 transmits a TB PPDU in response to the trigger frame, the TB PPDU is transmitted through an RU indicated by the RU allocation field 1320. In this case, the RU indicated by the RU allocation field 1320 may be an RU shown in FIG. 5, FIG. 6, and FIG. 7.

The subfield of FIG. 13 may include a coding type field 1330. The coding type field 1330 may indicate a coding type of the TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to ‘1’, and when LDPC coding is applied, the coding type field 1330 may be set to ‘0’.

In addition, the subfield of FIG. 13 may include an MCS field 1340. The MCS field 1340 may indicate an MCS scheme applied to the TB PPDU. For example, when BCC coding is applied to the TB PPDU, the coding type field 1330 may be set to ‘1’, and when LDPC coding is applied, the coding type field 1330 may be set to ‘0’.

Hereinafter, a UL OFDMA-based random access (UORA) scheme will be described.

FIG. 14 describes a technical feature of the UORA scheme.

A transmitting STA (e.g., an AP) may allocate six RU resources through a trigger frame as shown in FIG. 14. Specifically, the AP may allocate a 1st RU resource (AID 0, RU 1), a 2nd RU resource (AID 0, RU 2), a 3rd RU resource (AID 0, RU 3), a 4th RU resource (AID 2045, RU 4), a 5th RU resource (AID 2045, RU 5), and a 6th RU resource (AID 3, RU 6). Information related to the AID 0, AID 3, or AID 2045 may be included, for example, in the user identifier field 1310 of FIG. 13. Information related to the RU 1 to RU 6 may be included, for example, in the RU allocation field 1320 of FIG. 13. AID=0 may imply a UORA resource for an associated STA, and AID=2045 may imply a UORA resource for an un-associated STA. Accordingly, the 1st to 3rd RU resources of FIG. 14 may be used as a UORA resource for the associated STA, the 4th and 5th RU resources of FIG. 14 may be used as a UORA resource for the un-associated STA, and the 6th RU resource of FIG. 14 may be used as a typical resource for UL MU.

In the example of FIG. 14, an OFDMA random access backoff (OBO) of a STA1 is decreased to 0, and the STA1 randomly selects the 2nd RU resource (AID 0, RU 2). In addition, since an OBO counter of a STA2/3 is greater than 0, an uplink resource is not allocated to the STA2/3. In addition, regarding a STA4 in FIG. 14, since an AID (e.g., AID=3) of the STA4 is included in a trigger frame, a resource of the RU 6 is allocated without backoff.

Specifically, since the STA1 of FIG. 14 is an associated STA, the total number of eligible RA RUs for the STA1 is 3 (RU 1, RU 2, and RU 3), and thus the STA1 decreases an OBO counter by 3 so that the OBO counter becomes 0. In addition, since the STA2 of FIG. 14 is an associated STA, the total number of eligible RA RUs for the STA2 is 3 (RU 1, RU 2, and RU 3), and thus the STA2 decreases the OBO counter by 3 but the OBO counter is greater than 0. In addition, since the STA3 of FIG. 14 is an un-associated STA, the total number of eligible RA RUs for the STA3 is 2 (RU 4, RU 5), and thus the STA3 decreases the OBO counter by 2 but the OBO counter is greater than 0.

FIG. 15 illustrates an example of a channel used/supported/defined within a 2.4 GHz band.

The 2.4 GHz band may be called in other terms such as a first band. In addition, the 2.4 GHz band may imply a frequency domain in which channels of which a center frequency is close to 2.4 GHz (e.g., channels of which a center frequency is located within 2.4 to 2.5 GHz) are used/supported/defined.

A plurality of 20 MHz channels may be included in the 2.4 GHz band. 20 MHz within the 2.4 GHz may have a plurality of channel indices (e.g., an index 1 to an index 14). For example, a center frequency of a 20 MHz channel to which a channel index 1 is allocated may be 2.412 GHz, a center frequency of a 20 MHz channel to which a channel index 2 is allocated may be 2.417 GHz, and a center frequency of a 20 MHz channel to which a channel index N is allocated may be (2.407+0.005*N) GHz. The channel index may be called in various terms such as a channel number or the like. Specific numerical values of the channel index and center frequency may be changed.

FIG. 15 exemplifies 4 channels within a 2.4 GHz band. Each of 1st to 4th frequency domains 1510 to 1540 shown herein may include one channel. For example, the 1st frequency domain 1510 may include a channel 1 (a 20 MHz channel having an index 1). In this case, a center frequency of the channel 1 may be set to 2412 MHz. The 2nd frequency domain 1520 may include a channel 6. In this case, a center frequency of the channel 6 may be set to 2437 MHz. The 3rd frequency domain 1530 may include a channel 11. In this case, a center frequency of the channel 11 may be set to 2462 MHz. The 4th frequency domain 1540 may include a channel 14. In this case, a center frequency of the channel 14 may be set to 2484 MHz.

FIG. 16 illustrates an example of a channel used/supported/defined within a 5 GHz band.

The 5 GHz band may be called in other terms such as a second band or the like. The 5 GHz band may imply a frequency domain in which channels of which a center frequency is greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used/supported/defined. Alternatively, the 5 GHz band may include a plurality of channels between 4.5 GHz and 5.5 GHz. A specific numerical value shown in FIG. 16 may be changed.

A plurality of channels within the 5 GHz band include an unlicensed national information infrastructure (UNII)-1, a UNII-2, a UNII-3, and an ISM. The INII-1 may be called UNII Low. The UNII-2 may include a frequency domain called UNII Mid and UNII-2 Extended. The UNII-3 may be called UNII-Upper.

A plurality of channels may be configured within the 5 GHz band, and a bandwidth of each channel may be variously set to, for example, 20 MHz, 40 MHz, 80 MHz, 160 MHz, or the like. For example, 5170 MHz to 5330 MHz frequency domains/ranges within the UNII-1 and UNII-2 may be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domains/ranges may be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domains/ranges may be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domains/ranges may be divided into one channel through a 160 MHz frequency domain.

FIG. 17 illustrates an example of a channel used/supported/defined within a 6 GHz band.

The 6 GHz band may be called in other terms such as a third band or the like. The 6 GHz band may imply a frequency domain in which channels of which a center frequency is greater than or equal to 5.9 GHz are used/supported/defined. A specific numerical value shown in FIG. 17 may be changed.

For example, the 20 MHz channel of FIG. 17 may be defined starting from 5.940 GHz. Specifically, among 20 MHz channels of FIG. 17, the leftmost channel may have an index 1 (or a channel index, a channel number, etc.), and 5.945 GHz may be assigned as a center frequency. That is, a center frequency of a channel of an index N may be determined as (5.940+0.005*N) GHz.

Accordingly, an index (or channel number) of the 2 MHz channel of FIG. 17 may be 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. In addition, according to the aforementioned (5.940+0.005*N) GHz rule, an index of the 40 MHz channel of FIG. 17 may be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

Although 20, 40, 80, and 160 MHz channels are illustrated in the example of FIG. 17, a 240 MHz channel or a 320 MHz channel may be additionally added.

Hereinafter, a PPDU transmitted/received in a STA of the present specification will be described.

FIG. 18 illustrates an example of a PPDU used in the present specification.

The PPDU of FIG. 18 may be referred to as various terms, such as EHT PPDU, transmitting PPDU, receiving PPDU, first type or Nth type PPDU, and so on. For example, in the present specification, PPDU or EHT PPDU may be referred to by using various terms, such as transmission PPDU, reception PPDU, first type or Nth type PPDU, and so on. Additionally, the EHT PPDU may be used in an EHT system and/or a new WLAN system, which is an enhanced version of the EHT system.

The PPDU of FIG. 18 may represent part or all of a PPDU type that is used in an EHT system. For example, the example of FIG. 18 may be used for both single-user (SU) mode and multi-user (MU) mode, or may be used only for the SU mode, or may be used only for the MU mode. For example, in the EHT system, a trigger-based (TB) PPDU may be separately defined or may be configured based on an example of FIG. 18. A trigger frame and UL-MU operations that are started by the trigger frame (e.g., transmitting operations of the TB PPDU), which are described by at least one of FIG. 10 to FIG. 14, may be directly applied to the EHT system without modification.

In FIG. 18, L-STF to EHT-LTF may be referred to as a preamble or physical preamble, and the L-STF to EHT-LTF may be generated/transmitted/received/obtained/decoded in a physical layer.

Subcarrier spacing of the L-LTF, L-STF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields of FIG. 18 may be determined as 312.5 kHz, and subcarrier spacing of the EHT-STF, EHT-LTF, Data fields may be determined as 78.125 kHz. That is, tone indexes (or subcarrier indexes) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be indicated in 312.5 kHz units, and tone indexes (or subcarrier indexes) of the EHT-STF, EHT-LTF, Data fields may be indicated in 78.125 kHz units.

In the PPDU of FIG. 18, L-LTF and L-STF may be the same as the fields of the prior art (or related art).

The L-SIG field of FIG. 18 may, for example, include 24 bits of bit information. For example, the 24-bit information may include a 4-bit Rate field, 1 Reserved bit, a 12-bit Length field, 1 Parity bit, and 6 Tail bits. For example, the 12-bit Length field may include information related to a PPDU length or time duration. For example, a value of the 12-bit Length field may be determined based on a type of the PPDU. For example, in case the PPDU is a non-HT PPDU, an HT PPDU, a VHT PPDU, or an EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, in case the PPDU is an HE PPDU, the value of the Length field may be determined as “a multiple of 3+1” or “a multiple of 3+2”. In other words, a value of the Length field for a non-HT PPDU, an HT PPDU, a VHT PPDU, or an EHT PPDU may be determined as a multiple of 3, and a value of the Length field for an HE PPDU may be determined as “a multiple of 3+1” or “a multiple of 3+2”.

For example, a transmitting STA may apply BCC encoding, which is based on a 1/2-code rate for 24-bit information of the L-SIG field. Afterwards, the transmitting STA may obtain 48 bits of BCC encoding bits. Then, BPSK modulation may be applied to the 48 encoding bits so as to generate 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to positions excluding a pilot subcarrier {Subcarrier indexes −21, −7, +7, +21} and a DC subcarrier {Subcarrier index 0}. As a result, the 48 BPSK symbols may be mapped to subcarrier indexes −26 to −22, −20 to −8, −6 to −1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map a signal of {−1, −1, −1, 1} to subcarrier indexes {−28, −27, +27, +28}. The aforementioned signal may be used for channel estimation for a frequency domain corresponding to {−28, −27, +27, +28}.

The transmitting STA may generate an RL-SIG, which is generated identically as the L-SIG. The receiving STA may know that the reception PPDU is an HE PPDU or EHT PPDU based on the presence (or existence) of an RL-SIG.

A Universal SIG (U-SIG) may be inserted after the RL-SIG of FIG. 18. The U-SIG may also be referred to by using various terms, such as a first SIG field, a first SIG, a first-type SIG, a control signal, a control signal field, a first (type) control signal, and so on.

The U-SIG may include N-bit information and may also include information for identifying the EHT PPDU type. For example, the U-SIG may be configured based on 2 symbols (e.g., two contiguous OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG may have a duration of 4 us. Each symbol of the U-SIG may be used for transmitting 26-bit information. For example, each symbol of the U-SIG may be transmitted/received based on 52 data tones and 4 pilot tones.

For example, A-bit information (e.g., 52 un-coded bits) may be transmitted through the U-SIG (or U-SIG field), and a first symbol of the U-SIG may transmit first X-bit information (e.g., 26 un-coded bits) among the total of A bits of the corresponding information, and a second symbol of the U-SIG may transmit remaining Y-bit information (e.g., 26 un-coded bits) of the A-bit information. For example, the transmitting STA may obtain 26 un-coded bits that are included in each U-SIG symbol. The transmitting STA may perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1/2 so as to generate 52-coded bits, and, then, the transmitting STA may perform interleaving on the 52-coded bits. The transmitting STA may perform BPSK modulation on the interleaved 52-coded bits, so as to generate 52 BPSK symbols that are allocated to each U-SIG symbol. One U-SIG symbol may be transmitted based on 56 tones (subcarriers) starting from subcarrier index −28 to subcarrier index +28, with the exception for DC index 0. The 52 BPSK symbols that are generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) excluding the pilot tones −21, −7, +7, +21 tones.

For example, the A-bit information (e.g., 52 un-coded bits) may include a CRC field (e.g., 4-bit length field) and a Tail field (e.g., 6-bit length field). The CRC field and the Tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on the 26 bits being allocated to the first symbol of the U-SIG and the remaining 16 bits excluding the CRC/Tail fields from the second symbol. And, the CRC field may be generated based on the related art CRC calculation algorithm. Additionally, the Tail field may be used for terminating a trellis of a convolutional decoder and may, for example, be configured as “000000”.

The A-bit information (e.g., 52 un-coded bits) being transmitted by the U-SIG (or U-SIG field) may be divided into version-independent bits and version-dependent bits. For example, a size of the version-independent bits may be fixed or variable. For example, the version-independent bits may be allocated only to the first symbol of the U-SIG or may be allocated to both the first and second symbols of the U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by using various terms, such as a first control bit and a second control bit.

For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmission/reception PPDU. For example, a first value of the 3-bit PHY version identifier may indicate that the transmission/reception PPDU is an EHT PPDU. In other words, when the transmitting STA transmits the EHT PPDU, the transmitting STA may set the 3-bit PHY version identifier to the first value. In other words, based on the PHY version identifier having the first value, the receiving STA may determine that the reception PPDU is an EHT PPDU.

For example, the version-independent bits of the U-SIG may include a 1-bit UL/DL flag field. A first value of the 1-bit UL/DL flag field is related to UL communication, and a second value of the 1-bit UL/DL flag field is related to DL communication.

For example, the version-independent bits of the U-SIG may include information related to the length of a TXOP, and information related to BSS color ID.

For example, in case the EHT PPDU is divided into various types (e.g., EHT PPDU related to SU mode, EHT PPDU related to MU mode, EHT PPDU related to a Trigger Frame, EHT PPDU related to Extended Range transmission, and so on), information related to the EHT PPDU type may be included in the version-dependent bits of the U-SIG.

For example, the U-SIG may include information related to 1) a bandwidth field including information related to a bandwidth, 2) a field including information related to an MCS scheme being applied to the EHT-SIG, 3) an indication field including information related to whether or not a dual subcarrier modulation (DCM) scheme is applied to the EHT-SIG, 4) a field including information related to a number of symbols being used for the EHT-SIG, 5) a field including information related to whether or not the EHT-SIG is generated throughout the whole band, 6) a field including information related to an EHT-LTF/STF type, 7) a field indicating an EHT-LTF length and a CP length.

Preamble puncturing may be applied to the PPDU of FIG. 18. Preamble puncturing means applying puncturing to a partial band (e.g., a Secondary 20 MHz band) of the whole band of a PPDU. For example, when an 80 MHz PPDU is transmitted, the STA may apply puncturing to a secondary 20 MHz band of the 80 MHz band and may transmit the PPDU only through a primary 20 MHz band and a secondary 40 MHz band.

For example, a pattern of preamble puncturing may be preset (or predetermined). For example, when a first puncturing pattern is applied, the puncturing may be applied only for a secondary 20 MHz band within the 80 MHz band. For example, when a second puncturing pattern is applied, the puncturing may be applied to only one of the two secondary 20 MHz bands that are included in the secondary 40 MHz band within the 80 MHz band. For example, when a third puncturing pattern is applied, the puncturing may be applied only to a secondary 20 MHz band that is included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band). For example, when a fourth puncturing pattern is applied, and when a primary 40 MHz band that is included in a primary 80 MHz band within a 160 MHz band (or 80+80 MHz band) is present, the puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

Information related to the preamble puncturing that is applied to the PPDU may be included in the U-SIG and/or EHT-SIG. For example, a first field of the U-SIG may include information related to a contiguous bandwidth of the PPDU, and a second field of the U-SIG may include information related to preamble puncturing that is applied to the PPDU.

For example, the U-SIG and EHT-SIG may include information related to preamble puncturing based on the following method. When the bandwidth of a PPDU exceeds 80 MHz, the U-SIG may be separately configured in 80 MHz units. For example, when the bandwidth of a PPDU is 160 MHz, a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band may be included in the corresponding PPDU. In this case, a first field of the first U-SIG may include information related to the 160 MHz bandwidth, and a second field of the first U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern) that is applied to the first 80 MHz band. Additionally, a first field of the second U-SIG may include information related to the 160 MHz bandwidth, and a second field of the second U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern) that is applied to the second 80 MHz band. Meanwhile, an EHT-SIG that is contiguous to the first U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern) that is applied to the second 80 MHz band, and an EHT-SIG that is contiguous to the second U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern) that is applied to the first 80 MHz band.

Additionally or alternatively, the U-SIG and EHT-SIG may include information related to preamble puncturing based on the following method. The U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern) for all bands. That is, the EHT-SIG may not include information related to preamble puncturing, and only the U-SIG may include information related to preamble puncturing (i.e., information related to a preamble puncturing pattern).

The U-SIG may be configured of 20 MHz units. For example, when an 80 MHz PPDU is configured, the U-SIG may be duplicated. That is, 4 identical U-SIGs may be included in the 80 MHz PPDU. A PPDU that exceeds the 80 MHz bandwidth may include different U-SIGs.

The EHT-SIG of FIG. 18 may include the technical features of an HE-SIG-B, which is indicated in the examples of FIG. 8 to FIG. 9, as they are. The EHT-SIG may also be referred to by using various terms, such as a second SIG field, a second SIG, a second-type SIG, a control signal, a control signal field, a second (type) control signal, and so on.

The EHT-SIG may include N-bit information (e.g., 1-bit information) related to whether an EHT PPDU supports the SU mode or whether an EHT PPDU supports the MU mode.

The EHT-SIG may be configured based on various MCS schemes. As described above, the information related to the MCS scheme being applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on a DCM scheme. For example, among N number of data tones (e.g., 52 data tones) that are allocated for the EHT-SIG, a first modulation scheme may be applied to one half of contiguous tones, and a second modulation scheme may be applied to the remaining half of contiguous tones. That is, the transmitting STA may modulate specific control information to a first symbol based on the first modulation scheme and may allocate the modulated first symbol to one half of contiguous tones. Thereafter, the transmitting STA may modulate the same control information to a second symbol based on the second modulation scheme and may allocated the modulated second symbol to the other half of contiguous tones. As described above, information related to whether or not the DCM scheme is applied to the EHT-SIG (e.g., 1 bit field) may be included in the U-SIG. EHT-STF of FIG. 18 may be used for enhancing automatic gain control estimation in a multiple input multiple output (MIMO) environment or OFDMA environment. And, EHT-LTF of FIG. 18 may be used for estimating a channel in a MIMO environment or OFDMA environment.

The EHT-STF may be set to various types. For example, among the STFs, a first type (i.e., 1x STF) may be generated based on a first type STF sequence in which non-zero coefficients are positioned at 16 subcarrier spacings. An STF signal that is generated based on the first type STF sequence may have a periodicity (or cycle period) of 0.8 μs. And, the signal having the periodicity of 0.8 μs may be repeated 5 times and become a first type STF having a length of 4 μs. For example, among the STFs, a second type (i.e., 2x STF) may be generated based on a second type STF sequence in which non-zero coefficients are positioned at 8 subcarrier spacings. An STF signal that is generated based on the second type STF sequence may have a periodicity (or cycle period) of 1.6 μs. And, the signal having the periodicity of 1.6 μs may be repeated 5 times and become a second type STF having a length of 8 μs. Hereinafter, an example of a sequence (i.e., EHT-STF sequence) for configuring an EHT-STF will be proposed. The following sequence may be modified to various types.

The EHT-STF may be configured based on the following M sequence.

M={−1,−1,−1,1,1,1,−1,1,1,1,−1,1,1,−1,1}  <Equation 1>

An EHT-STF for a 20 MHz PPDU may be configured based on the following equation. The example shown below may be a first type (i.e., 1x STF) sequence. For example, the first type sequence may be included in an EHT-PPDU and not a trigger-based (TB) PPDU. In the following equation, (a:b:c) may denote durations being defined at b tone spacings (i.e., subcarrier spacings) starting from an a tone index (i.e., subcarrier index) to a c tone index. For example, Equation 2 shown below may represent a sequence that is defined at 16 tone spacings starting from tone index −112 to tone index 112. For an EHT-STF, since subcarrier spacing of 78.125 kHz is applied, the 16 tone spacings may mean that EHT-STF coefficients (or elements) are positioned at 78.125*16=1250 kHz intervals (or spacings). Additionally, * means multiplication (i.e., ‘multiplied by’), and sqrt( ) means square root.

EHT-STF(−112:16:112)={M}*(1+j)/sqrt(2)  <Equation 2>

EHT-STF(0)=0

An EHT-STF for a 40 MHz PPDU may be configured based on the following equation. The example shown below may be a first type (i.e., 1x STF) sequence.

EHT-STF(−240:16:240)={M,0,−M}*(1+j)/sqrt(2)  <Equation 3>

An EHT-STF for an 80 MHz PPDU may be configured based on the following equation. The example shown below may be a first type (i.e., 1x STF) sequence.

EHT-STF(−496:16:496)={M,1,−M,0,−M,1,−M}*(1+j)/sqrt(2)  <Equation 4>

An EHT-STF for a 160 MHz PPDU may be configured based on the following equation. The example shown below may be a first type (i.e., 1x STF) sequence.

EHT-STF(−1008:16:1008)={M,1,−M,0,−M,1,−M,0,−M,−1,M,0,−M,1,−M}*(1+j)/sqrt(2)  <Equation 5>

In the EHT-STF for an 80+80 MHz PPDU, a sequence for a lower 80 MHz may be the same as Equation 4. And, in the EHT-STF for the 80+80 MHz PPDU, a sequence for a higher 80 MHz may be configured based on the following equation.

EHT-STF(−496:16:496)={−M,−1,M,0,−M,1,−M}*(1+j)/sqrt(2)  <Equation 6>

Hereinafter, Equation 7 to Equation 11 relate to examples of a second type (i.e., 2 x STF) sequence.

EHT-STF(−120:8:120)={M,0,−M}*(1+j)/sqrt(2)  <Equation 7>

An EHT-STF for a 40 MHz PPDU may be configured based on the following equation.

EHT-STF(−248:8:248)={M,−1,−M,0,M,−1,M}*(1+j)/sqrt(2)  <Equation 8>

EHT-STF(−248)=0

EHT-STF(248)=0

An EHT-STF for an 80 MHz PPDU may be configured based on the following equation.

EHT-STF(−504:8:504)={M,−1,M,−1,−M,−1,M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)  <Equation 9>

An EHT-STF for a 160 MHz PPDU may be configured based on the following equation.

EHT-STF(−1016:16:1016)={M,−1,M,−1,−M,−1,M,0,−M,1,M,1,−M,1,−M,0,−M,1,−M,1,M,1,−M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)  <Equation 10>

EHT-STF(−8)=0, EHT-STF(8)=0,

EHT-STF(−1016)=0, EHT-STF(1016)=0

In the EHT-STF for an 80+80 MHz PPDU, a sequence for a lower 80 MHz may be the same as Equation 9. And, in the EHT-STF for the 80+80 MHz PPDU, a sequence for a higher 80 MHz may be configured based on the following equation.

EHT-STF(−504:8:504)={−M,1,−M,1,M,1,−M,0,−M,1,M,1,−M,1,−M}*(1+j)/sqrt(2)  <Equation 11>

EHT-STF(−504)=0,

EHT-STF(504)=0

An EHT-LTF may have first, second, and third types (i.e., 1x, 2x, 4x LTF). For example, the first/second/third type LTF may be generated based on an LTF sequence in which non-zero coefficients are positioned at 4/2/1 subcarrier spacing(s). The first/second/third type LTF may have a time length of 3.2/6.4/12.8 μs. Additionally, various lengths of GI (e.g., 0.8/1/6/3.2 μs) may be applied to the first/second/third type LTF.

Information related to an STF and/or LTF type (including information related to GI that is applied to the LTF) may be included in an SIG A field and/or SIG B field of FIG. 18.

The PPDU (i.e., EHT-PPDU) of FIG. 18 may be configured based on examples of FIG. 5 and FIG. 6.

For example, an EHT PPDU being transmitted over a 20 MHz band, i.e., a 20 MHz EHT PPDU, may be configured based on RUs of FIG. 5. That is, the location of an RU of the EHT-STF, EHT-LTF, data field being included in the EHT PPDU may be determined as shown in FIG. 5.

An EHT PPDU being transmitted over a 40 MHz band, i.e., a 40 MHz EHT PPDU, may be configured based on RUs of FIG. 6. That is, the location of an RU of the EHT-STF, EHT-LTF, data field being included in the EHT PPDU may be determined as shown in FIG. 6.

Since the RU location of FIG. 6 corresponds to 40 MHz, if the pattern of FIG. 6 is repeated two times, a tone plan for 80 MHz may be determined. That is, an 80 MHz EHT PPDU may be transmitted based on a new tone plan in which the RU of FIG. 6 is repeated two times, and not the RU of FIG. 7.

In case the pattern of FIG. 6 is repeated two times, 23 tones (i.e., 11 guard tones+12 guard tones) may be configured in a DC region. That is, a tone plan for an 80 MHz EHT PPDU being allocated based on OFDMA may have 23 DC tones. On the other hand, an 80 MHz EHT PPDU being allocated based on non-OFDMA (i.e., non-OFDMA full Bandwidth 80 MHz PPDU) may be configured based on 996 RUs and may include 5 DC tones, 12 left-guard tones, and 11 right-guard tones.

A tone plan for 160/240/320 MHz may be configured to have a format of repeating the pattern of FIG. 6 multiple times.

The PPDU of FIG. 18 may be determined (or identified) as an EHT PPDU based on the following method.

A receiving STA may determine a type of an RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the EHT PPDU: 1) when a first symbol after an L-LTF signal of the RX PPDU is a BPSK symbol; 2) when RL-SIG in which the L-SIG of the RX PPDU is repeated is detected; and 3) when a result of applying “module 3” to a value of a length field of the L-SIG of the RX PPDU is detected as “0”. When the RX PPDU is determined as the EHT PPDU, the receiving STA may detect a type of the EHT PPDU (e.g., an SU/MU/Trigger-based/Extended Range type), based on bit information included in a symbol after the RL-SIG of FIG. 18. In other words, the receiving STA may determine the RX PPDU as the EHT PPDU, based on: 1) a first symbol after an L-LTF signal, which is a BPSK symbol; 2) RL-SIG contiguous to the L-SIG field and identical to L-SIG; 3) L-SIG including a length field in which a result of applying “modulo 3” is set to “0”; and 4) a 3-bit PHY version identifier of the aforementioned U-SIG (e.g., a PHY version identifier having a first value).

For example, the receiving STA may determine the type of the RX PPDU as the EHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the HE PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; 2) when RL-SIG in which the L-SIG is repeated is detected; and 3) when a result of applying “module 3” to a value of a length field of the L-SIG is detected as “1” or “2”.

For example, the receiving STA may determine the type of the RX PPDU as a non-HT, HT, and VHT PPDU, based on the following aspect. For example, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU: 1) when a first symbol after an L-LTF signal is a BPSK symbol; and 2) when RL-SIG in which L-SIG is repeated is not detected. In addition, even if the receiving STA detects that the RL-SIG is repeated, when a result of applying “modulo 3” to the length value of the L-SIG is detected as “0”, the RX PPDU may be determined as the non-HT, HT, and VHT PPDU.

In the following example, a signal represented as a (TX/RX/UL/DL) signal, a (TX/RX/UL/DL) frame, a (TX/RX/UL/DL) packet, a (TX/RX/UL/DL) data unit, (TX/RX/UL/DL) data, or the like may be a signal transmitted/received based on the PPDU of FIG. 18. The PPDU of FIG. 18 may be used to transmit/receive frames of various types. For example, the PPDU of FIG. 18 may be used for a control frame. An example of the control frame may include a request to send (RTS), a clear to send (CTS), a power save-poll (PS-poll), BlockACKReq, BlockAck, a null data packet (NDP) announcement, and a trigger frame. For example, the PPDU of FIG. 18 may be used for a management frame. An example of the management frame may include a beacon frame, a (re-)association request frame, a (re-)association response frame, a probe request frame, and a probe response frame. For example, the PPDU of FIG. 18 may be used for a data frame. For example, the PPDU of FIG. 18 may be used to simultaneously transmit at least two or more of the control frame, the management frame, and the data frame.

1. Tone Plan in 802.11ax WLAN System

In the present specification, a tone plan relates to a rule for determining a size of a resource unit (RU) and/or a location of the RU. Hereinafter, a PPDU based on the IEEE 802.11ax standard, that is, a tone plan applied to an HE PPDU, will be described. In other words, hereinafter, the RU size and RU location applied to the HE PPDU are described, and control information related to the RU applied to the HE PPDU is described.

In the present specification, control information related to an RU (or control information related to a tone plan) may include a size and location of the RU, information of a user STA allocated to a specific RU, a frequency bandwidth for a PPDU in which the RU is included, and/or control information on a modulation scheme applied to the specific RU. The control information related to the RU may be included in an SIG field. For example, in the IEEE 802.11ax standard, the control information related to the RU is included in an HE-SIG-B field. That is, in a process of generating a TX PPDU, a transmitting STA may allow the control information on the RU included in the PPDU to be included in the HE-SIG-B field. In addition, a receiving STA may receive an HE-SIG-B included in an RX PPDU and obtain control information included in the HE-SIG-B, so as to determine whether there is an RU allocated to the receiving STA and decode the allocated RU, based on the HE-SIG-B.

In the IEEE 802.11ax standard, HE-STF, HE-LTF, and data fields may be configured in unit of RUs. That is, when a first RU for a first receiving STA is configured, STF/LTF/data fields for the first receiving STA may be transmitted/received through the first RU.

In the IEEE 802.11ax standard, a PPDU (i.e., SU PPDU) for one receiving STA and a PPDU (i.e., MU PPDU) for a plurality of receiving STAs are separately defined, and respective tone plans are separately defined. Specific details will be described below.

The RU defined in 11ax may include a plurality of subcarriers. For example, when the RU includes N subcarriers, it may be expressed by an N-tone RU or N RUs. A location of a specific RU may be expressed by a subcarrier index. The subcarrier index may be defined in unit of a subcarrier frequency spacing. In the 11ax standard, the subcarrier frequency spacing is 312.5 kHz or 78.125 kHz, and the subcarrier frequency spacing for the RU is 78.125 kHz. That is, a subcarrier index +1 for the RU may mean a location which is more increased by 78.125 kHz than a DC tone, and a subcarrier index −1 for the RU may mean a location which is more decreased by 78.125 kHz than the DC tone. For example, when the location of the specific RU is expressed by [−121:−96], the RU may be located in a region from a subcarrier index −121 To a subcarrier index −96. As a result, the RU may include 26 subcarriers.

The N-tone RU may include a pre-set pilot tone.

2. Null Subcarrier and Pilot Subcarrier

A subcarrier and resource allocation in the 802.11ax system will be described.

An OFDM symbol consists of subcarriers, and the number of subcarriers may function as a bandwidth of a PPDU. In the WLAN 802.11 system, a data subcarrier used for data transmission, a pilot subcarrier used for phase information and parameter tacking, and an unused subcarrier not used for data transmission and pilot transmission are defined.

An HE MU PPDU which uses OFDMA transmission may be transmitted by mixing a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, and a 996-tone RU.

Herein, the 26-tone RU consists of 24 data subcarriers and 2 pilot subcarriers. The 52-tone RU consists of 48 data subcarriers and 4 pilot subcarriers. The 106-tone RU consists of 102 data subcarriers and 4 pilot subcarriers. The 242-tone RU consists of 234 data subcarriers and 8 pilot subcarriers. The 484-tone RU consists of 468 data subcarriers and 16 pilot subcarriers. The 996-tone RU consists of 980 data subcarriers and 16 pilot subcarriers.

1) Null Subcarrier

As shown in FIG. 5 to FIG. 7, a null subcarrier exists between 26-tone RU, 52-tone RU, and 106-tone RU locations. The null subcarrier is located near a DC or edge tone to protect against transmit center frequency leakage, receiver DC offset, and interference from an adjacent RU. The null subcarrier has zero energy. An index of the null subcarrier is listed as follows.

Channel Width RU Size Null Subcarrier Indices 20 MHz 26, 52 ±69, ±122 106 none 242 none 40 MHz 26, 52 ±3, ±56, ±57, ±110, ±137, ±190, ±191, ±244 106 ±3, ±110, ±137, ±244 242, 484 none 80 MHz 26, 52 ±17, ±70, ±71, ±124, ±151, ±204, ±205, ±258, ±259, ±312, ±313, ±366, ±393, ±446, ±447, ±500 106 ±17, ±124, ±151, ±258,±259, ±366, ±393, ±500 242, 484 none 996 none 160 MHz  26, 52, 106 {null subcarrier indices in 80 MHz − 512, null subcarrier indices in 80 MHz + 512} 242, 484, 996, none 2 × 996

A null subcarrier location for each 80 MHz frequency segment of the 80+80 MHz HE PPDU shall follow the location of the 80 MHz HE PPDU.

2) Pilot Subcarrier

If a pilot subcarrier exists in an HE-LTF field of HE SU PPDU, HE MU PPDU, HE ER SU PPDU, or HE TB PPDU, a location of a pilot sequence in an HE-LTF field and data field may be the same as a location of 4× HE-LTF. In 1× HE-LTF, the location of the pilot sequence in HE-LTF is configured based on pilot subcarriers for a data field multiplied 4 times. If the pilot subcarrier exists in 2× HE-LTF, the location of the pilot subcarrier shall be the same as a location of a pilot in a 4× data symbol. All pilot subcarriers are located at even-numbered indices listed below.

Channel Width RU Size Pilot Subcarrier Indices 20 MHz 26, 52 ±10, ±22, ±36, ±48, ±62, ±76, ±90, ±102, ±116 106, 242 ±22, ±48, ±90, ±116 40 MHz 26, 52 ±10, ±24, ±36, ±50, ±64, ±78, ±90, ±104, ±116, ±130, ±144, ±158, ±170, ±184, ±198, ±212, ±224, ±238 106, 242, 484 ±10, ±36, ±78, ±104, ±144, ±170, ±212, ±238

Channel Width RU Size Pilot Subcarrier Indices 80 MHz 26, 52 ±10, ±24, ±38, ±50, ±64, ±78, ±92, ±104, ±118, ±130, ±144, ±158, ±172, ±184, ±198, ±212, ±226, ±238, ±252, ±266, ±280, ±292, ±306, ±320, ±334, ±346, ±360, ±372, ±386, ±400, ±414, ±426, ±440, ±454, ±468, ±480, ±494 106, 242, 484 ±24, ±50, ±92, ±118, ±158, ±184, ±226, ±252, ±266, ±292, ±334, ±360, ±400, ±426, ±468, ±494 996 ±24, ±92, ±158, ±226, ±266, ±334, ±400, ±468 160 MHz  26, 52, 106, 242, {pilot subcarrier indices in 484 80 MHz − 512, pilot subcarrier indices in 80 MHz + 512} 996 {for the lower 80 MHz, pilot subcarrier indices in 80 MHz − 512, for the upper 80 MHz, pilot subcarrier indices in 80 MHz + 512}

At 160 MHz or 80+80 MHz, the location of the pilot subcarrier shall use the same 80 MHz location for 80 MHz of both sides.

3. HE Transmit Procedure and Low Density Parity Check (LDPC) Tone Mapping

In an 802.11ax wireless local area network (WLAN) system, transmission procedures (or transmit procedures) in a physical layer (PHY) include a procedure for an HE Single User (SU) PPDU, a transmission procedure for an HE extended range (ER) SU PPDU, a transmission procedure for an HE Multi User (MU) PPDU, and a transmission procedure for an HE trigger-based (TB) PPDU. A FORMAT field of a PHY-TXSTART.request(TXVECTOR) may be the same as HE_SU, HE_MU, HE_ER_SU or HE_TB. The transmission procedures do not describe operations of optional features, such as Dual Carrier Modulation (DCM). Among the diverse transmission procedures, FIG. 21 shows only the PHY transmission procedure for the HE SU PPDU.

FIG. 19 shows an example of a PHY transmission procedure for HE SU PPDU.

In order to transmit data, the MAC generates a PHY-TXSTART.request primitive, which causes a PHY entity to enter a transmit state. Additionally, the PHY is configured to operate in an appropriate frequency via station management through PLME. Other transmission parameters, such as HE-MCS, coding type, and transmission power are configured through a PHY-SAP by using a PHY-TXSTART.request(TXVECTOR) primitive. After transmitting a PPDU that transfers (or communicates) a trigger frame, a MAC sublayer may issue a PHY-TRIGGER.request together with a TRIGVECTOR parameter, which provides information needed for demodulating an HE TB PPDU response that is expected of the PHY entity.

The PHY indicates statuses of a primary channel and another channel via PHY-CCA.indication. The transmission of a PPDU should be started by the PHY after receiving the PHY-TXSTART.request(TXVECTOR) primitive.

After a PHY preamble transmission is started, the PHY entity immediately initiates data scrambling and data encoding. An encoding method for the data field is based on FEC_CODING, CH_BANDWIDTH, NUM_STS, STBC, MCS, and NUM_USERS parameters of the TXVECTOR.

A SERVICE field and a PSDU are encoded in a transmitter (or transmitting device) block diagram, which will be described later on. Data should be exchanged between the MAC and the PHY through a PHY-DATA.request(DATA) primitive that is issued by the MAC and PHY-DATA. confirm primitives that are issued by the PHY. A PHY padding bit is applied to the PSDU in order to set a number of bits of the coded PSDU to be an integer multiple of a number of coded bits per OFDM symbol.

The transmission is swiftly (or quickly) ended by the MAC through a PHY-TXEND.request primitive. The PSDU transmission is ended upon receiving a PHY-TXEND.request primitive. Each PHY-TXEND.request primitive mat notify its reception together with a PHY-TXEND.confirm primitive from the PHY.

A packet extension and/or a signal extension may exist in a PPDU. A PHY-TXEND.confirm primitive is generated at an actual end time of a most recent PPDU, an end time of a packet extension, and an end time of a signal extension.

In the PHY, a Guard Interval (GI) that is indicated together with a GI duration in a GI_TYPE parameter of the TXVECTOR is inserted in all data OFDM symbols as a solution for a delay spread.

If the PPDU transmission is completed, the PHY entity enters a receive state.

FIG. 20 shows an example of a block diagram of a transmitting device for generating each field of an HE PPDU.

In order to generate each field of the HE PPDU, the following block diagrams are used.

a) pre-FEC PHY padding

b) Scrambler

c) FEC (BCC or LDPC) encoders

d) post-FEC PHY padding

e) Stream parser

f) Segment parser (for contiguous 160 MHz and non-contiguous 80+80 MHz transmission)

g) BCC interleaver

h) Constellation mapper

i) DCM tone mapper

j) Pilot insertion

k) Replication over multiple 20 MHz (for BW>20 MHz)

l) Multiplication by 1st column of PHE-LTF

m) LDPC tone mapper

n) Segment deparser

o) Space time block code (STBC) encoder for one spatial stream

p) Cyclic shift diversity (CSD) per STS insertion

q) Spatial mapper

r) Frequency mapping

s) Inverse discrete Fourier transform (IDFT)

t) Cyclic shift diversity (CSD) per chain insertion

u) Guard interval (GI) insertion

v) Windowing

FIG. 20 shows a block diagram of a transmitting device (or transmitter block diagram) that is used for generating a data field of an HE Single User (SU) PPDU having LDPC encoding applied thereto and being transmitted at a 160 MHz. If the transmitter block diagram is used for generating a data field of an HE SU PPDU that is transmitted in an 80+80 MHz band, a segment deparser is not used as shown in FIG. 22. That is, the block diagram of the transmitter (or transmitting device) is used per 80 MHz band in a situation where the band is divided into an 80 MHz band and another 80 MHz band by using a segment parser.

Data fields of an HE SU PPDU, an HE extended range (ER) SU PPDU, and an HE trigger-based (TB) PPDU may be configured as described below via LDPC encoding.

-   -   a) Construct the SERVICE field as described in 27.3.12.3         (SERVICE field) and append the PSDU to the SERVICE field.     -   b) Pre-FEC padding: Append the pre-FEC padding bits as described         in 27.3.12 (Data field). There are no tail bits.     -   c) Scrambler: Scramble the pre-FEC padded data.     -   d) LDPC encoder: LDPC encode as described in 27.3.12.5.2 (LDPC         coding).     -   e) Post-FEC padding Append the post-FEC pad bits and PE field as         described in 27.3.12 (Data field).     -   f) Stream parser: Rearrange the output of LDPC encoder into         blocks as described in 27.3.12.6 (Stream parser).     -   g) Segment parser (if needed): In a 160 MHz or 80+80 MHz         transmission with a 2×996-tone RU, divide the output of each         stream parser into two frequency subblocks as described in         27.3.12.6 (Stream parser). This block is bypassed for 20 MHz, 40         MHz, and 80 MHz transmissions.     -   h) Constellation mapper Map to BPSK, BPSK DCM, QPSK, QPSK DCM,         16-QAM. 16-QAM DCM, 64-QAM, 256-QAM, or 1024-QAM constellation         points as described in 27.3.12.9 (Constellation mapping).     -   i) LDPC tone mapper: the LDPC tone mapping shall be performed on         all LDPC encoded streams as described in 27.3.12.10 (LDPC tone         mapper).     -   j) Segment deparser (if needed): In 160 MHz transmission, merge         the two frequency subblocks into one frequency segment as         described in 27.3.12.11 (Segment deparser). Tins block is         bypassed for 20 MHz, 40 MHz, 80 MHz, and 80+80 MHz         transmissions.     -   k) STBC: Apply STBC as described in 27.3.12.12 (Space-time block         coding).     -   l) Pilot insertion: Insert pilots following the steps described         in 27.3.12.13 (Pilot subcarriers).     -   m) CSD: Apply CSD for each space-time stream and frequency         segment as described in 27.3.11.2.2 (Cyclic shift for HE         modulated fields).     -   n) Spatial mapping: Apply the Q matrix as described in         27.3.12.14 (OFDM modulation)     -   o) IDFT: In an 80-180 MHz transmission, map each frequency         subblock to a separate IDFT. Compute the inverse discrete         Fourier transform.     -   p) Insert GI and apply windowing: Prepend a GI determined by the         TXVECTOR parameter GI_TYPE and apply windowing as described in         27.3.10 (Mathematical description of signals).     -   q) Analog and RF: Upconvert the resulting complex baseband         waveform with each transmit chain to an RF signal according to         the center frequency of the desired channel and transmit Refer         to 27.3.10 (Mathematical description of signals) and 27.3.11 (HE         preamble) for details.

Referring to FIG. 20, a data field (or data bit sequence) may be encoded in an LDPC encoder. A data bit sequence that is inputted to the LDPC encoder may be in a scrambled state by a scrambler.

The encoded data bit sequence that is encoded by the LDPC encoder is divided into multiple spatial streams by a stream parser. At this point, an encoded data bit sequence that is divided into each spatial stream may be referred to as a spatial block. A number of the spatial blocks may be determined by a number of spatial streams that are used for transmitting an PPDU, and the number of spatial blocks may be set to be equal to the number of spatial blocks.

Each spatial block is divided into at least one or more data segments by the segment parser. As shown in FIG. 22, when a data field is transmitted in a 160 MHz band, the 160 MHz band is divided into two 80 MHz bands, and the spatial block is divided into a first data segment and a second data segment for each 80 MHz band. Thereafter, the first and second data segments may each be processed with constellation mapping and LDPC mapping for each 80 MHz band.

In an HE MU transmission, except for cyclic shift diversity (CSD) being performed based on knowledge of a corresponding user on a space-time stream start index, a PPDU encoding processor is independently performed in a resource unit (RU) per user up to the input of a spatial mapping block. All user data of the RU is coupled with a transmit chain of a spatial mapping block and then mapped.

Hereinafter, LDPC tone mapping will be described.

LDPC tone mapping should be performed in all LDPC-coded streams by using an LDPC tone mapping distance parameter D_(TM). D_(TM) is a constant for each bandwidth and is given a value for each band, as shown below. LDPC tone mapping should not be performed for an encoded stream by using BCC.

160 MHz, Parameter 20 MHz 40 MHz 80 MHz 80 + 80 MHz D_(TM) 4 6 9 9

For a VHT PPDU transmission, LDPC tone mapping for an LDPC-coded stream related to a user u may be performed, as shown below, by substituting a stream of complex numbers generated by a constellation mapper.

${{{d_{{t(k)},i,n,l,u}^{''} = d_{k,i,n,l,u}^{\prime}};{k = 0}},1,\ldots,{N_{SD} - {1{for}20{MHz}}},{40{MHz}},{{{80{MHz}{and}80} + {80{MHz}}};}}{{k = 0},1,\ldots,{{\frac{\overset{.}{N_{SD}}}{2} - {\overset{.}{1}{for}160{MHz}}};}}{{i = 1},\ldots,{N_{{SS},u};}}{{n = 0},1,\ldots,{{N_{SYM} - 1};}}\ {{l = {0{for}20{MHz}}},{40{MHz}},{{{and}80{MHz}};}}{{l = 0},{{{1{for}160{MHz}{and}80} + {80{MHz}}};}}{{u = 0},\ldots,{N_{user} - 1}}{where}{{t(k)} = \left\{ \begin{matrix} {{{D_{TM}\left( {k{mod}\frac{N_{SD}}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}} \right\rfloor},} & \begin{matrix} {{{for}20{MHz}},{40{MHz}},} \\ {{80{MHz}},{{{and}80} + {80{MHz}}}} \end{matrix} \\ {{{D_{TM}\left( {k{mod}\frac{N_{SD}/2}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}/2} \right\rfloor},} & {{for}160{MHz}} \end{matrix} \right.}$

As a result of the LDPC tone mapping operation, each of two consecutively generated complex constellation numbers d^(k,i,n,l,u)′ and d^(k+1,i,n,l,u)′ may be transmitted from two data tones, respectively, each data tone being spaced apart by at least D_(TM)−1. For example, d^(k,i,n,l,u)′ may be transmitted from a first data tone, d^(k+1,i,n,l,u)′ may be transmitted from a second data tone, and the first data tone and the second data tone may be spaced apart by D_(TM)−1. The aforementioned operation is the same as performing block-interleaving on complex numbers d^(0,i,n,l,u)′, . . . , d^(NSD-1,i,n,l,u)′ for variables i, n, and u by using a matrix having a D_(TM) row and a N_(SD)/D_(TM) column (for 20 MHz, 40 MHz, 80 MHz or 80+80 MHz) or N_(SD)/2*D_(TM) column (for 160 MHz). At this point, d^(0,i,n,l,u)′, . . . , d^(NSD-1,i,n,l,u)′ are written row-wise in the matrix, and d^(0,i,n,l,u)′, . . . , d^(NSD-1,i,n,l,u)′ are read column-wise from the matrix.

LDPC tone mapping is separately performed for an upper 80 MHz and a lower 80 MHz of a 160 MHz or 80+80 MHz transmission that is indicated by frequency subblock index 1.

Since LDPC tone mapping is not performed for a BCC-coded stream, the following equation may be applied to the BCC-coded stream.

${{{d_{k,i,n,l,u}^{''} = d_{k,i,n,l,u}^{\prime}};{k = 0}},1,\ldots,{N_{SD} - {1{for}20{MHz}}},{40{MHz}},{{{80{MHz}{and}80} + {80{MHz}}};}}{{k = 0},1,\ldots,{{\frac{\overset{.}{N_{SD}}}{2} - {\overset{.}{1}{for}160{MHz}}};}}{{i = 1},\ldots,{N_{{SS},u};}}{{{n = 0},1,\ldots,{{N_{SYM} - 1};}}\ }{{l = {0{for}20{MHz}}},{40{MHz}},{{{and}80{MHz}};}}{{l = 0},{{{1{for}160{MHz}{and}80} + {80{MHz}}};}}{{u = 0},\ldots,{N_{user} - 1}}$

Additionally, LDPC tone mapping should be performed in all LDPC-coded streams that are mapped to a resource unit (RU). LDPC tone mapping should not be performed on a stream having used BCC. When DCM is applied to an LDPC-coded stream, D_(TM_DCM) should be applied to both a lower half data subcarrier of the RU and an upper half data subcarrier of the RU. LDPC tone mapping distance parameters D_(TM) and D_(TM_DCM) are constant values for each of an RU size and another RU size,

RU Size (tones) Parameter 26 52 106 242 484 996 2 × 996 D_(TM) 1 3 6 9 12 20 20 D_(TM) _(—) _(DCM) 1 1 3 9 9 14 14

LDPC tone mapping distance parameters D_(TM) and D_(TM_DCM) are applied to a frequency subblock 1=0 and frequency subblock 1=1, respectively.

For an HE PPDU without DCM, in an r-th RU, LDPC tone mapping for an LDPC-coded stream related to a user u may be performed, as shown below, by substituting a stream of complex numbers generated by a constellation mapper.

${d_{{t(k)},i,n,l,r,u}^{''} = d_{k,i,n,l,r,u}^{\prime}}{where}{k = \left\{ {{{\begin{matrix} {0,1,\ldots,{N_{SD} - 1}} & \begin{matrix} {{{for}a26 -},{52 -},{106 -},{242 -}} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {0,1,\ldots,{{N_{SD}/2} - 1}} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}i} = 1},\ldots,{{N_{{SS},r,u}n} = 0},1,\ldots,{{N_{SYM} - {1l}} = \left\{ {{{\begin{matrix} 0 & \begin{matrix} {{{for}a26 -},52,{106 -},{242 -},} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {0,1} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}u} = 0},\ldots,{{N_{{user},r} - {1r}} = 0},\ldots,{{N_{RU} - {1N_{SD}{is}{the}{number}{of}{data}{tones}{in}{the}r - {th}{RU}{t(k)}}} = \left\{ \begin{matrix} {{{D_{TM}\left( {k{mod}\frac{N_{SD}}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}} \right\rfloor},} & \begin{matrix} {{{for}a26 -},{52 -},{106 -},{242 -}} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {{{D_{TM}\left( {k{mod}\frac{N_{SD}/2}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}/2} \right\rfloor},} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix} \right.}} \right.}} \right.}$

For an HE PPDU having DCM applied in a Data field, in an r-th RU, LDPC tone mapping for an LDPC-coded stream related to a user u may be performed, as shown below, by substituting a stream of complex numbers generated by a constellation mapper.

${d_{{t(k)},i,n,l,r,u}^{''} = d_{k,i,n,l,r,u}^{\prime}}{where}{k = \left\{ {{{\begin{matrix} {0,1,\ldots,{{2N_{SD}} - 1}} & {{{for}a26 -},{52 -},{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {0,1,\ldots,{N_{SD} - 1}} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}i} = 1},\ldots,{N_{{SS},r,u}{n = 0}},1,\ldots,{{N_{SYM} - {1l}} = \left\{ {{{\begin{matrix} 0 & {{{for}a26 -},52,{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {0,1} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}u} = 0},\ldots,{{N_{{user},r} - {1r}} = 0},\ldots,{N_{RU} - {1N_{SD}{is}{the}{number}{of}{data}{tones}{in}{the}r - {th}{RU}{if}{DCM}{is}{appplied}{For}a26 -}},{52 -},{106 -},{242 -},{{484 - {and}996 - {tone}{RU}{t(k)}} = \left\{ {{\begin{matrix} {{{D_{TM\_ DCM}\left( {k{mod}\frac{N_{SD}}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM\_ DCM}}{N_{SD}} \right\rfloor},} & {{{for}k} < N_{SD}} \\ {{{D_{TM\_ DCM}\left( {\left( {k - N_{SD}} \right){mod}\frac{N_{SD}}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{\left( {k - N_{SD}} \right) \cdot D_{TM\_ DCM}}{N_{SD}} \right\rfloor + N_{SD}},} & {{{for}k} \geq N_{SD}} \end{matrix}{For}a2 \times 996 - {tone}{RU}},{{t(k)} = \left\{ {\begin{matrix} {{{D_{TM\_ DCM}\left( {k{mod}\frac{N_{SD}/2}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM\_ DCM}}{N_{SD}/2} \right\rfloor},} & {{{for}0} \leq k < {N_{SD}/2}} \\ \begin{matrix} {{D_{TM\_ DCM}\left( {\left( {k - {N_{SD}/2}} \right){mod}\frac{N_{SD}/2}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{\left( {k - {N_{SD}/2}} \right) \cdot D_{TM\_ DCM}}{N_{SD}/2} \right\rfloor +} \\ {{N_{SD}/2},} \end{matrix} & {{{for}{N_{SD}/2}} \leq k < N_{SD}} \end{matrix}D_{TM\_ DCM}{is}{the}{LDPC}{tone}{mapping}{distance}{for}{the}r - {th}{RU}{if}{DCM}{is}{{applied}.}} \right.}} \right.}} \right.}} \right.}$

An LDPC tone mapper for a 26-, 52-, 106-, 242-, 484- and 996-tone is defined as one segment. LDPC tone mapping is separately performed for upper 80 MHz and lower 80 MHz frequency segments of a 2×996-tone RU that is indicated by frequency subblock index 1.

Since LDPC tone mapping is not performed for a BCC-coded stream, the following equation may be applied to the BCC-coded stream.

${d_{k,i,n,l,r,u}^{''} = d_{k,i,n,l,r,u}^{\prime}}{where}{k = \left\{ {{{\begin{matrix} {0,1,\ldots,{N_{SD} - 1}} & \begin{matrix} {{{for}a26 -},{52 -},{106 -},{242 -}} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {0,1,\ldots,{{N_{SD}/2} - 1}} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}i} = 1},\ldots,{{N_{{SS},r,u}n} = 0},1,\ldots,{{N_{SYM} - {1l}} = \left\{ {{{\begin{matrix} 0 & \begin{matrix} {{{for}a26 -},52,{106 -},{242 -},} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {0,1} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}u} = 0},\ldots,{{N_{{user},r} - {1r}} = 0},\ldots,{N_{RU} - 1}} \right.}} \right.}$

A brief description of the concept of LDPC tone mapping, which is described in the present specification, is as follows.

When data rate of a related art WLAN data packet increases, a length of an LDPC codeword (LCW) may become shorter than N_CBPS (a number of bits within an OFDM symbol). In this case, an LDPC-coded bit is transmitted to some tones or subcarriers. And, accordingly, a problem of failing to ensure sufficient frequency diversity may occur.

FIG. 21 shows an example of an LDPC tone mapping operation.

In the present specification, LDPC tone mapping may mean a mapping scheme for mapping an LDPC-coded stream at an interval (or spacing) of a specific tone or subcarrier. The present specification describes an example of setting tone spacing (D_TM) to 4, 6, 9, and so on, in accordance with a bandwidth (BW) of a PPDU. For example, FIG. 23 is an example of LDPC tone mapping having tone spacing (D_TM) set to 3. That is, an operation that is similar to an interleaving operation may be performed through the LDPC tone mapping.

For example, for a data field of a PPDU of the 802.11ac standard (i.e., VHT PPDU) or a PPDU of the 802.11ax standard (i.e., HE PPDU), the LDPC tone mapper may be positioned after the Constellation mapper. For example, in FIG. 22, an output of the Constellation mapper (i.e., contiguous Constellation symbols) may be mapped to a data tone that is separated at a spacing (or interval) of D_TM−1.

FIG. 22 shows an example of a DCM method being applied to data.

Meanwhile, in IEEE 802.11ax, a Dual Carrier/Sub-carrier Modulation (DCM) scheme is applied. A transmitting device (or transmitter) that is based on the DCM scheme may transmit the same information to different subcarriers. For example, the transmitting device may include a structure that is shown in FIG. 22. As shown in FIG. 22, first data information may be included in subcarrier K based on a first constellation mapping, i.e., modulation mapping 1. Additionally, the same first data information may be included in subcarrier K+N/2 based on a second constellation mapping, i.e., modulation mapping 2. The first constellation mapping and the second constellation mapping may be the same mapping scheme or may each be a different mapping scheme. In FIG. 22, variable N may also be N_SD, which is a number of data tones being included in an RU or frequency segment. Additionally, although the scheme of FIG. 24 is an example of a result of first/second constellation mappings that are applied to the same data being mapped to first/second tones, for example, it is possible for a result of first/second/third constellation mappings that are applied to the same data to be mapped to first/second/third tones, or it is possible for a result of first/second/ . . . /N-th constellation mappings that are applied to the same data to be mapped to first/second/ . . . /N-th tones.

The DCM scheme may be applied only to a data field and/or SIG-B field of an HE PPDU. Additionally, the DCM scheme may be used or may not be used in the transmitting device (optional feature).

A more detailed description of the DCM scheme of 11ax is as follows.

DCM is an optional modulation scheme for HE-SIG-B and data fields. DCM may be applied to an HE SU PPDU and an HE ER SU PPDU. In an HE MU PPDU or HE TB PPDU, DCM may be applied to an RU that includes data for one user and cannot be applied to an RU that includes data for multiple users.

DCM is applicable only for HE-MCS 0, 1, 3, and 4. DCM is applicable only for N_(SS)=1 or N_(SS)=2 (In case of a single user RU in an HE MU PPDU, N_(SS),r,u=1 or N_(SS),r,u=2). DCM is not applicable together with MU-MIMO or STBC.

When DCM is used, a bit sequence is mapped to one symbol pair (d_(k)′, d_(q(k))′). In order to use a frequency diversity for a 996-tone RU or a smaller RU, k has a range of 0<=k<=N_(SD)−1, and q(k) has a range of N_(SD)<=q(k)<=2N_(SD)−1. For a 2×996-tone RU, k has a range of 0<=k<=N_(SD)/2−1, and q(k) has a range of N_(SD)/2<=q(k)<=N_(SD)−1. In order to maximize the frequency diversity, an index of a DCM subcarrier pair (k, q(k)) is q(k)=k+N_(SD) for a 996-tone RU or a smaller RU, and q(k)=k+N_(SD)/2 for a 2×996-tone RU. Herein, when DCM=1, N_(SD) is given a value of N_(SD). And, when DCM=0, N_(SD) is given a half value of N_(SD).

-   -   A modulation bit having DCM applied thereto may be described as         follows. For BPSK modulation with DCM, the input stream is         broken into groups of N_(CBPS) or N_(CBPS,u) bits (B₀, B₁, . . .         , B_(N) _(CBPS,u) ₋₁). Each bit B_(k) is BPSK modulated to a         sample d_(k)′. This generates the samples for the lower half of         the data subcarriers. For the upper half of the subcarriers, the         samples are generated as d_(k+N) _(SD) ′=d_(k)′×e^(j(k+N) ^(SD)         ^()π), k=0, 1, . . . , N_(SD)−1. The N_(SD) here refers to the         N_(SD) with DCM=1, which is half the value of N_(SD) with DCM=0.     -   For QPSK modulation with DCM, the input stream is broken into         groups of N_(CBPS) or N_(CBPS,u) bits (B₀, B₁, . . . , B_(N)         _(CBPS,u) ₁). Each pair of bits (B_(2k)B_(2k+1)) is QPSK         modulated to a symbol d_(k)′. This generates the constellation         points for the lower half the data subcarriers in the RU. For         the upper half of the data subcarriers in the RU, d_(k+N) _(SD)         ′=conj(d_(k)′), where conj( ) represents the complex conjugate         operation. The N_(SD) here refers to the N_(SD) with DCM=1,         which is half the value of N_(SD) with DCM=0.     -   For 16-QAM modulation with DCM, the input stream is broken into         groups of N_(CBPS) or N_(CBPS,u) bits (B₀, B₁, . . . , B_(N)         _(CBPS,u) ₋₁). A group of 4 bits (B_(4k), B_(4k+1), B_(4k+2),         B_(4k+3)) is 16-QAM modulated to a sample d_(k)′ as described in         17.3.5.8 (Subcarrier modulation mapping). This is the sample on         subcarrier k in the lower half. In the upper half, the sample         d_(k+N) _(SD) , on subcarrier k+N_(SD) is obtained by 16-QAM         modulating a per-mutation of the bits (B_(4k), B_(4k+1),         B_(4k+2), B_(4k+3)). Specifically, d_(k+N) _(SD) ′ is obtained         by applying the 16-QAM modulation procedure in 18.3; 5.8 to the         bit group (B_(4k+1), B_(4k), B_(4k+3), B_(4k+2)). The N_(SD)         here refers to the N_(SD) with DCM=1, which is half the Value of         N_(SD) with DCM=0.

In a non-OFDMA HE PPDU, a subcarrier allocation related variable for an HE-modulated field may be defined as a tone allocation related parameter for the non-OFDMA HE PPDU, as shown below.

Parameter CBW20 CBW40 CBW80 CBW80 + 80 CBW160 Description N_(SD) 234 468 980 980 1960 Number of data subcarriers per frequency segment N_(SP) 8 16 16 16 32 Number of pilot subcarriers per frequency segment N_(ST) 242 484 996 996 1992 Total number of subcarriers per frequency segment N_(SR) 122 244 500 500 1012 Highest data subcarrier index per frequency segment N_(Seg) 1 1 1 2 1 Number of frequency segments N_(DC) 3 5 5 5 23 Number of null subcarriers at DC per segment N_(Guard, Left) 6 12 12 12 12 Number of low frequency guard subcarriers N_(Guard, Right) 5 11 11 11 11 Number of high frequency guard subcarriers NOTE: N_(ST) = N_(SD) + N_(SP)

In an OFDMA HE PPDU, a subcarrier allocation related variable for an HE-modulated field may be defined as a tone allocation related parameter for the OFDMA HE PPDU, as shown below.

RU Size (subcarriers) Parameter 26 52 106 242 484 996 2 × 996 Description N_(SD) 24 48 102 234 468 980 1960 Number of data subcarriers per RU N_(SP) 2 4 4 8 16 16 32 Number of pilot subcarriers per RU N_(ST) 26 52 106 242 484 996 1992 Total number of subcarriers per RU NOTE: N_(ST) = N_(SD) + N_(SP)

As described above, N_(SD) may denote a number of data tones being included in one RU or frequency segment (e.g., 20/40/80/160 MHz segment).

Parameters that are frequently used in an 802.11ax WLAN system may be defined as follows.

Symbol Explanation N_(RU) For pre-HE modulated fields, N_(RU) = 1. For HE modulated fields, N_(RU) represents the number of occupied RUs in the transmission. N_(user,r) For pre-HE modulated fields, N_(user,r) = 1. For HE modulated fields, N_(user,r) represents the total number of users in the r-th occupied RU of the transmission. N_(user,total) Total number of users in all occupied RUs of an HE transmission, i.e., $N_{{user},{total}} = {\sum\limits_{r - 0}^{N_{RU} - 1}N_{{user},r}}$ N_(CBPS), N_(CBPS,u) Number of coded bits per OFDM symbol for user u, u = 0, . . . , N_(user,total) − 1 For an HE SU PPDU and HE ER SU PPDU, N_(CBPS) = N_(CBPS,0) For an HE MU PPDU, N_(CBPS) is undefined N_(CBPSS), N_(CBPSS,u) Number of coded bits per OFDM symbol per spatial stream for user u, u = 0, . . . , N_(user,total) − 1. For the Data field of an HE SU PPDU and HE ER SU PPDU, N_(CBPSS) = N_(CBPSS,0) For the Data field of an HE MU PPDU, N_(CBPSS) is undefined N_(DBPS), N_(DBPS,u) Number of data bits per OFDM symbol for user u, u = 0, . . . , N_(user,total) − 1. For an HE SU PPDU and HE ER SU PPDU, N_(DBPS) = N_(DBPS,0) For an HE MU PPDU, N_(DBPS) is undefined

Hereinafter, operations having LDPC tone mapping performed therein will be described in detail.

FIG. 23 shows an example of LDPC tone mapping having tone spacing set to 3 in a 52-tone RU in a situation where DCM is not applied.

FIG. 23 shows an example of LDPC tone mapping being performed without DCM for a 52-tone RU. According to the description presented above, k is a constellation mapped tone index that is outputted from the constellation mapper, and t(k) is an LDPC tone mapped tone index that is outputted from the LDPC tone mapper. According to the table that is presented above, D_(TM)=3 and N_(SD)=48 for the 52-tone RU.

A complex constellation number d_(k,i,n,l,r,u)′ that is outputted from the constellation mapper may obtain a complex constellation number d^(t(k),i,n,l,u)″ that is outputted via LDPC tone mapping, which is similar to the interleaving operation. Thus, it may be known that the d^(k,i,n,l,u)′ along with d^(t(k),i,n,l,u)″ mapped in data tones that are spaced apart by D_(TM)−1. That is, as a result of the LDPC tone mapping operation, each of the two serially (or consecutively) generated complex constellation numbers may be transmitted from two data tones each being spaced apart by D_(TM)−1, respectively.

Referring to FIG. 23, since LDPC tone mapping for a 52-tone RU is performed, and since k=0, 1, . . . , 47 and l=0, a segment parser is not performed. And, since t(k)=D_(TM)*(k mod N_(SD)/D_(TM))+[k*D_(TM)/N_(SD)] for the 52-tone RU, the tone index may be separated by a spacing (or interval) of D_(TM)−1, as shown below.

k=0->t(k)=0

k=1->t(k)=3

k=2->t(k)=6

. . .

k=15->t(k)=45

k=16->t(k)=1 (return back up and restart interleaving from k=16)

k=17->t(k)=4

k=18->t(k)=7

. . .

k=46->t(k)=44

k=47->t(k)=47

FIG. 24 shows an example of LDPC tone mapping having tone spacing set to 3 in a 106-tone RU in a situation where DCM is applied.

FIG. 24 shows an example of LDPC tone mapping being performed by applying DCM for a 106-tone RU. According to the description presented above, k is a constellation mapped tone index that is outputted from the constellation mapper, and t(k) is an LDPC tone mapped tone index that is outputted from the LDPC tone mapper. According to the table that is presented above, D_(TM_DCM)=3 and N_(SD)=51 for the 106-tone RU.

A complex constellation number d^(k,i,n,l,u)′ that is outputted from the constellation mapper may obtain a complex constellation number d^(t(k),i,n,l,u)″ that is outputted via LDPC tone mapping, which is similar to the interleaving operation. Thus, it may be known that the d_(k,i,n,l,r,u)′ along with d^(t(k),i,n,l,u)″ is mapped in data tones that are spaced apart by D_(TM)−1. That is, as a result of the LDPC tone mapping operation, each of the two serially (or consecutively) generated complex constellation numbers may be transmitted from two data tones each being spaced apart by D_(TM)−1, respectively.

Referring to FIG. 24, since LDPC tone mapping for a 106-tone RU is performed, and since k=0, 1, . . . , 101 and l=0, a segment parser is not performed. However, since DCM is applied in this case, when k<N_(SD) (lower half data subcarrier) for the 106-tone RU, since t(k)=D_(TM_DCM)*(k mod N_(SD)/D_(TM_DCM))+[k*D_(TM_DCM)/N_(SD)], and, when k>=N_(SD) (upper half data subcarrier), since t(k)=D_(TM_DCM)*((k−N_(SD))mod N_(SD)/D_(TM_DCM))+[(k−N_(SD))*D_(TM_DCM)/N_(SD)], the tone index may be separated by a spacing (or interval) of D_(TM)−1 per lower half data subcarrier and upper half data subcarrier, as shown below.

<Lower Half Data Subcarrier>

k=0->t(k)=0

k=1->t(k)=3

k=2->t(k)=6

. . .

k=16->t(k)=48

k=17->t(k)=1 (return back up and restart interleaving from k=17)

. . .

k=50->t(k)=50

<upper half data subcarrier>

k=51->t(k)=51

k=52->t(k)=54

. . .

k=101->t(k)=101

4. Embodiment Applicable to the Present Disclosure

The WLAN 802.11 system supports transmission of an increased stream using a band wider than that of the existing 11ax or more antennas to increase the peak throughput. The present disclosure also considers a method of using aggregation of various bands.

The present disclosure proposes a tone mapping method for a situation where LDPC channel coding is applied when a PPDU is transmitted by allocating a Multi-RU to one STA.

In the existing 802.11ax, data may be transmitted using a 26/52/106/242/484/996/2×996-tone RU, and in this case, BCC or LDPC may be used for channel coding. In particular, when LDPC is used, LDPC tone mapping may be used for frequency diversity, and the PPDU encoding process and LDPC tone mapping when LDPC is applied are described in detail with reference to FIGS. 21 to 26.

In the existing 802.11ax system, one STA is allocated only one RU, but the 802.11be introduces a method called Multi-RU so that one STA may be allocated several RUs rather than one RU. Accordingly, an STA may transmit a PPDU using a plurality of RUs, thereby improving throughput. The EHT-SIG field of FIG. 18 may provide information for allocating a Multi-RU.

The U-SIG of FIG. 18 is composed of version-independent fields and version-dependent fields. Also, U-SIG consists of two symbols that are jointly encoded, and each 20 MHz consists of 52 data tones and 4 pilot tones. Also, the U-SIG field is modulated in the same way as HE-SIG-A. The EHT-SIG may be divided into a common field and a user-specific field and may be encoded according to a variable MCS. The information for allocating RUs may be carried in the common field and the user-specific field.

In other words, when LDPC channel coding is applied in a situation where a PPDU is transmitted using a Multi-RU, the LDPC tone mapping method may be defined as follows.

4.1 Application of LDPC Tone Mapping within Each RU

N_(SD), D_(TM), and D_(TM_DCM) in each RU are as follows. Here, since LDPC tone mapping is performed on each RU of a Multi-RU, the N_(SD), D_(TM), and D_(TM_DCM) for each RU size described above may be used without modification.

RU Size (subcarriers) Parameter 26 52 106 242 484 996 2 × 996 Description N_(SD) 24 48 102 234 468 980 1960 Number of data subcarriers per RU N_(SP) 2 4 4 8 16 16 32 Number of pilot subcarriers per RU N_(ST) 26 52 106 242 484 996 1992 Total number of subcarriers per RU NOTE: N_(ST) = N_(SD) + N_(SP)

RU Size (tones) Parameter 26 52 106 242 484 996 2 × 996 D_(TM) 1 3 6 9 12 20 20 D_(TM) _(—) _(DCM) 1 1 3 9 9 14 14

In this case, frequency diversity may be obtained by applying LDPC tone mapping for each RU of a Multi-RU allocated using the existing equations below.

${d_{{t(k)},i,n,l,r,u}^{''} = d_{k,i,n,l,r,u}^{\prime}}{where}{k = \left\{ {{{\begin{matrix} {0,1,\ldots,{N_{SD} - 1}} & {{{for}a26 -},{52 -},{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {0,1,\ldots,{{N_{SD}/2} - 1}} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}i} = 1},\ldots,{{N_{{SS},r,u}n} = 0},1,\ldots,{{N_{SYM} - {1l}} = \left\{ {{{\begin{matrix} 0 & \begin{matrix} {{{for}a26 -},52,{106 -},{242 -},} \\ {484 - {and}996 - {tone}{RU}} \end{matrix} \\ {0,1} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}u} = 0},\ldots,{{N_{{user},r} - {1r}} = 0},\ldots,{{N_{RU} - {1N_{SD}{is}{the}{number}{of}{data}{tones}{in}{the}r - {th}{RU}{t(k)}}} = \left\{ {{\begin{matrix} {{{D_{TM}\left( {k{mod}\frac{N_{SD}}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}} \right\rfloor},} & {{{for}a26 -},{52 -},{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {{{D_{TM}\left( {k{mod}\frac{N_{SD}/2}{D_{TM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM}}{N_{SD}/2} \right\rfloor},} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}d_{{t(k)},i,n,l,r,u}^{''}} = {{d_{k,i,n,l,r,u}^{\prime}{where}k} = \left\{ {{{\begin{matrix} {0,1,\ldots,{{2N_{SD}} - 1}} & {{{for}a26 -},{52 -},{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {0,1,\ldots,{N_{SD} - 1}} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}i} = 1},\ldots,{{N_{{SS},r,u}n} = 0},1,\ldots,{{N_{SYM} - {1l}} = \left\{ {{{\begin{matrix} 0 & {{{for}a26 -},52,{106 -},{242 -},{484 - {and}996 - {tone}{RU}}} \\ {0,1} & {{for}a2 \times 996 - {tone}{RU}} \end{matrix}u} = 0},\ldots,{{N_{{user},r} - {1r}} = 0},\ldots,{N_{RU} - {1N_{SD}{is}{the}{number}{of}{data}{tones}{in}{the}r - {th}{RU}{if}{DCM}{is}{appplied}{For}a26 -}},{52 -},{106 -},{242 -},{{484 - {and}996 - {tone}{RU}{t(k)}} = \left\{ {{\begin{matrix} {{{D_{TM\_ DCM}\left( {k{mod}\frac{N_{SD}}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM\_ DCM}}{N_{SD}} \right\rfloor},} & {{{for}k} < N_{SD}} \\ {{{D_{TM\_ DCM}\left( {\left( {k - N_{SD}} \right){mod}\frac{N_{SD}}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{\left( {k - N_{SD}} \right) \cdot D_{TM\_ DCM}}{N_{SD}} \right\rfloor + N_{SD}},} & {{{for}k} \geq N_{SD}} \end{matrix}{For}a2 \times 996 - {tone}{RU}},{{t(k)} = \left\{ {\begin{matrix} {{{D_{TM\_ DCM}\left( {k{mod}\frac{N_{SD}/2}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{k \cdot D_{TM\_ DCM}}{N_{SD}/2} \right\rfloor},} & {{{for}0} \leq k < {N_{SD}/2}} \\ \begin{matrix} {{D_{TM\_ DCM}\left( {\left( {k - {N_{SD}/2}} \right){mod}\frac{N_{SD}/2}{D_{TM\_ DCM}}} \right)} + \left\lfloor \frac{\left( {k - {N_{SD}/2}} \right) \cdot D_{TM\_ DCM}}{N_{SD}/2} \right\rfloor +} \\ {{N_{SD}/2},} \end{matrix} & {{{for}{N_{SD}/2}} \leq k < N_{SD}} \end{matrix}D_{TM\_ DCM}{is}{the}{LDPC}{tone}{mapping}{distance}{for}{the}r - {th}{RU}{if}{DCM}{is}{{applied}.}} \right.}} \right.}} \right.}} \right.}} \right.}} \right.}} \right.}$

At this time, to perform LDPC tone mapping for each RU in the Multi-RU, the Multi-RU has to be divided into each RU by the segment parser of FIG. 20. In other words, when the data field is transmitted in the Multi-RU, the Multi-RU is divided for each frequency segment by the segment parser, and the LDPC tone mapping (constellation mapping is also possible) may be performed for each frequency segment. In this case, the size of one frequency segment may be the size of each RU of the Multi-RU.

However, the 802.11be introduced the concept of Large RU and Small RU, where Large RU means an RU having the size of a 242 tone RU or more, and Small RU means an RU having the size less than a 242 tone RU. When a combination of Large RUs constitutes a Multi-RU, the segment parser may be applied to divide the Multi-RUs into each RU, and LDPC tone mapping may be performed on each RU.

However, if the size of the Multi-RU is within 80 MHz even though the Multi-RU comprises a combination of Large RUs, the segment parser may not be applied, but the LDPC tone mapping may be performed as in the method of 4.2 described later by considering the Multi-RU to be one RU. For example, since the total size of the 242+484 tone RU is smaller than the 80 MHz band, it is not divided into each RU, and LDPC tone mapping is performed by considering the 242+484 tone RU to be one RU.

Also, when the size of a Multi-RU is within 80 MHz even though the Multi-RU is a combination of Small RUs or a combination of Small RUs and Large RUs, the Multi-RU is not divided into each RU but is considered to be one RU for which LDPC tone mapping may be performed (the segment parser is not applied to the Multi-RU).

4.2 Application of Tone Mapping to the Entire Allocated RUs

When a Multi-RU is allocated to one STA, N_(SD), D_(TM), and D_(TM_DCM) in the Multi-RU (or New RU) may be defined. However, when a plurality of RUs are combined, scheduling, signaling, and hardware complexity for the combination are increased. Therefore, only two RUs may be allocated to one STA, and a Multi-RU (or a New RU) formed by a combination of two RUs and N_(SD), D_(TM), and D_(TM_DCM) in the Multi-RU (or New RU) are proposed as follows. Although the Multi-RU above is defined as a New RU, two RUs are combined and considered as if the two RUs were one RU, which may be considered to have been allocated to one STA. Accordingly, LDPC encoding may be performed using one encoder by considering a combination of RUs to be one RU rather than performed for each RU of the New RU. Also, the LDPC tone mapper may be newly defined by considering the sizes of the entire allocated RUs as shown below, and frequency diversity may be obtained by applying LDPC tone mapping to the New RU.

2 × 26 + 26 + 26 + 26 + 26 + 26 52 106 242 484 996 tone tone tone tone tone tone New RU RU RU RU RU RU RU N_(SD) 48 72 126 258 492 1004 D_(TM) 3 3/4/6 6/7/9 6 12 4/251 D_(TM) _(—) _(DCM) 1 1/2/3 3/7/9 6 12 4/251

2 × 52 52 + 106 52 + 242 52 + 484 52 + 996 New RU tone RU tone RU tone RU tone RU tone RU N_(SD) 96 150 282  516  1028 D_(TM) 3/4/6  6 6 12 4/257 D_(TM) _(—) _(DCM) 1/2/3 3/6 6 12 4/257

2 × 106 106 + 242 106 + 484 106 + 996 New RU tone RU tone RU tone RU tone RU N_(SD) 204 336 570 1082 D_(TM)  6  12 15/19 2/541 D_(TM) _(—) _(DCM) 3/4/6  8  10 2/541

2 × 242 242 + 484 242 + 996 New RU tone RU tone RU tone RU N_(SD) 468 702 1214 D_(TM) 12 13/18 2/607 D_(TM) _(—) _(DCM) 9  13 2/607

2 × 484 484 + 996 New RU tone RU tone RU N_(SD) 936 1448 D_(TM) 12/13/18 8/181 D_(TM) _(—) _(DCM) 12/13 8/181

Also, LDPC tone mapping may be applied to the New RU using the existing equations in 4.1 without modification. However, values of k, l, and t(k) used in the existing equations of 4.1 may be configured according to the size of the New RU (or Multi-RU). A detailed embodiment will be described with reference to FIGS. 25 and 26.

The 802.11be may not support a combination of an RU smaller than 242 tone and an RU greater than or equal to 242 tone, and in particular, may consider only 26+52 tone RUs/26+106 tone RUs for a combination of RUs smaller than 242 tone. The 26/52/106 tone RUs aggregated with each other may be two adjacent RUs or two RUs in a 20 MHz channel. Alternatively, the 26/52/106 tone RUs aggregated with each other may be 52 tone RUs or 106 tone RUs adjacent to the center 26 tone RU in the 80 MHz tone plan. Considering the size of the LDPC tone mapper for existing RUs, it may be desirable to use 4 for D_(TM) and 2 for D_(TM_DCM) in a 26+52 tone RU, and 6, 3 (or 7, 3) for D_(TM) and D_(TM_DCM) in a 26+106 tone RU, respectively. Alternatively, since there is no significant difference in performance, it may be desirable to define the size of the LDPC tone mapper to be the same for the 26+52 tone RU and the 26+106 tone RU, which are combinations of RUs smaller than 242 tone, and D_(TM) may be defined as 6, and D_(TM_DCM) may be defined as 3.

In what follows, an operation for performing LDPC tone mapping in Multi-RU transmission will be described in detail.

FIG. 25 shows an example of LDPC tone mapping having tone spacing set to 18 in a 242+484 tone RU in a situation where DCM is not applied.

FIG. 25 shows an example in which LDPC tone mapping is performed on a 242+484 tone RU. According to the descriptions above, k represents a constellation mapped tone index output from the constellation mapper, and t(k) represents an LDPC tone mapped tone index output from the LDPC tone mapper. According to the table above, D_(TM)=18 and N_(SD)=702 for the 242+484 tone RU.

A complex constellation number d^(k,i,n,l,u)′ output from the constellation mapper may obtain a complex constellation number d^(t(k),i,n,l,u)″ output via LDPC tone mapping, which is similar to the interleaving operation. Thus, it may be known that the d^(k,i,n,l,u)′ along with d^(t(k),i,n,l,u)″ are mapped in data tones spaced apart by D_(TM)−1. That is, as a result of the LDPC tone mapping operation, two consecutively generated complex constellation numbers may be transmitted from two data tones separated from each other by D_(TM)−1.

Referring to FIG. 25, since LDPC tone mapping for a 242+484 tone RU is performed, k=0, 1, . . . , 701. And since the size of the 242+484 tone RU is smaller than 80 MHz, the segment parser is not performed (l=0). Since LDPC tone mapping is performed on the 242+484 tone RU using the equation that t(k)=D_(TM)*(k mod N_(SD)/D_(TM))+[k*D_(TM)/N_(SD)], the tone index may be separated by a spacing of D_(TM)−1 as follows.

k=0->t(k)=0

k=1->t(k)=18

k=2->t(k)=36

. . .

k=38->t(k)=684

k=39->t(k)=1 (the tone index returns back up and restarts interleaving from k=39)

k=40->t(k)=19

k=41->t(k)=37

. . .

k=663->t(k)=17

k=664->t(k)=35

. . .

k=701->t(k)=701

FIG. 26 shows an example of LDPC tone mapping having tone spacing set to 8 in a 2×484 tone RU in a situation where DCM is not applied.

FIG. 26 shows an example in which LDPC tone mapping is performed on a 2×484 (or 484+484) tone RU. According to the descriptions above, k represents a constellation mapped tone index output from the constellation mapper, and t(k) represents an LDPC tone mapped tone index output from the LDPC tone mapper. According to the table above, D_(TM)=12 and N_(SD)=936 for the 2×484 tone RU.

A complex constellation number d^(k,i,n,l,u)′ output from the constellation mapper may obtain a complex constellation number d^(t(k),i,n,l,u)″ output via LDPC tone mapping, which is similar to the interleaving operation. Thus, it may be known that the d^(k,i,n,l,u)′ along with d^(t(k),i,n,l,u)″ are mapped in data tones spaced apart by D_(TM)−1. That is, as a result of the LDPC tone mapping operation, two consecutively generated complex constellation numbers may be transmitted from two data tones separated from each other by D_(TM)−1.

Referring to FIG. 26, the segment parser is performed on the 2×484 tone RU to perform LDPC tone mapping for each RU (each RU may be distinguished from each other by l=0, 1). Accordingly, k for each 484 tone RU may be 0, 1, . . . , 467. Since LDPC tone mapping is performed on each 484 tone RU using the equation that t(k)=D_(TM)*(k mod (N_(SD)/2)/D_(TM))+[k*D_(TM)/(N_(SD)/2)], the tone index may be separated at intervals of D_(TM)−1 as follows. It is assumed that the 2×484 tone RU is composed of a first 484 tone RU (first RU) and a second 484 RU (second RU).

<First 484 Tone RU (First RU)>

k=0->t(k)=0

k=1->t(k)=12

k=2->t(k)=24

. . .

k=38->t(k)=456

k=39->t(k)=1 (the tone index returns back up and restarts interleaving from k=39)

k=40->t(k)=13

k=41->t(k)=15

. . .

k=429->t(k)=11

k=430->t(k)=23

. . .

k=467->t(k)=467

<Second 484 Tone RU (Second RU)>

k=0->t(k)=0

k=1->t(k)=12

k=2->t(k)=24

. . .

k=38->t(k)=456

k=39->t(k)=1 (the tone index returns back up and restarts interleaving from k=39)

k=40->t(k)=13

k=41->t(k)=15

. . .

k=429->t(k)=11

k=430->t(k)=23

. . .

k=467->t(k)=467

FIG. 27 is a flow diagram illustrating the operation of a transmitting apparatus according to the present embodiment.

A transmitting apparatus (an AP and/or a non-AP STA) may perform the example of FIG. 27. Part of the steps in the example of FIG. 27 may be omitted or modified.

For example, before FIG. 27 is performed, an AP and a non-AP STA may exchange capability information as to whether each STA supports LDPC tone mapping. For example, a beacon, a probe request, a probe response, an association request, an association response, other management frames, other control frames, or the MAC header of a general data PPDU may include the capability information as to whether LDPC tone mapping is supported.

The capability information related to LDPC tone mapping may have various values. For example, the capability information may have a first value when an STA does not support LDPC tone mapping; the capability information may have a second value when the STA supports LDPC-tone mapping according to a specific first method (for example, the method of 4.1 above); and the capability information may have a third value when the STA supports LDPC-tone mapping according to a specific second method (for example, the method of 4.2 above). Alternatively, when the STA supports LDPC tone mapping based on one of the methods above, the capability information on the LDPC tone mapping may have the first value while, when the STA does not support the LDPC tone mapping, the capability information may have the second value.

In the S2710 step, the transmitting apparatus (namely, a transmitting STA) may obtain information on the tone plane. As described above, information on the tone plan includes the size of an RU, control information related to the RU, information on a frequency band to which the RU belongs, and information on an STA that receives the RU.

In the S2720 step, the transmitting STA may configure/generate a PPDU based on the obtained control information. The step of configuring/generating the PPDU may include configuring/generating each field of the PPDU. In other words, the S2720 step includes configuring the EHT-SIG-A/B/C field that includes control information on the tone plan or sounding. That is, the 2720 step may include a step of configuring a field including control information (for example, N bitmap) indicating the size/position of the RU and/or a step of configuring a field including the identifier (for example, AID) of an STA that receives the RU.

Also, the S2720 step may include generating an STF/LTF sequence transmitted through a specific RU. The STF/LTF sequence may be generated based on a preconfigured STF generation sequence/LTF generation sequence.

Also, the S2720 step may include generating a data field (namely, MPDU) transmitted through a specific RU.

In the S2730 step, the transmitting apparatus may transmit a PPDU configured through the S2720 step to a receiving apparatus based on the S2730 step.

While performing the S2730 step, the transmitting apparatus may perform at least one of the CSD, spatial mapping, IDFT/IFFT, and GI insert operations.

The signal/field/sequence configured according to the present disclosure may be transmitted in the form of FIG. 18.

A method for configuring the data field of a PPDU may be performed based on the apparatus of FIG. 20 through the S2720 to S2730 steps.

As shown in the figure, the transmitting apparatus may perform 1) a PHY padding operation, 2) a scrambling operation, and 3) an LDPC encoding operation on a data bit string to be included in the data field. Afterward, the transmitting apparatus may perform 4) a stream parsing operation that maps LDPC encoded bits to a specific spatial stream, 5) a segment parsing operation that divides frequency segments if required, 6) a constellation mapping operation on the individual spatial streams and frequency segments, and 7) an LDPC tone mapping operation according to the present disclosure on the modulation symbols generated based on the constellation mapping.

Also, as shown in FIG. 1, a transmitting apparatus may include a memory 112, a processor 111, and a transceiver 113.

The memory 112 may store information on a plurality of tone plans/RUs according to the present disclosure.

The processor 111 may generate various RUs and configure PPDUs based on the information stored in the memory 112. FIG. 1 shows an example of a PPDU generated by the processor 111.

The processor 111 may perform the whole/part of the operations shown in FIG. 27.

The transceiver 113 shown in the figure may include an antenna and perform analog signal processing. Specifically, the processor 111 may control the transceiver 113 to transmit a PPDU generated by the processor 111.

Alternatively, the processor 111 may generate a transmitting PPDU and store information on the transmitting PPDU in the memory 112.

FIG. 28 is a flow diagram illustrating the operation of a receiving apparatus according to the present embodiment.

A receiving apparatus (an AP and/or a non-AP STA) may perform the example of FIG. 28.

A receiving STA or a receiving apparatus (an AP and/or a non-AP STA) may perform the example of FIG. 28. Part of the steps (or specific sub-steps to be described later) in the example of FIG. 28 may be omitted or modified.

For example, before FIG. 28 is performed, an AP and a non-AP STA may exchange capability information as to whether each STA supports LDPC tone mapping. For example, a beacon, a probe request, a probe response, an association request, an association response, other management frames, other control frames, or the MAC header of a general data PPDU may include the capability information as to whether LDPC tone mapping is supported.

The capability information related to LDPC tone mapping may have various values. For example, the capability information may have a first value when an STA does not support LDPC tone mapping; the capability information may have a second value when the STA supports LDPC-tone mapping according to a specific first method (for example, the method of 4.1 above); and the capability information may have a third value when the STA supports LDPC-tone mapping according to a specific second method (for example, the method of 4.2 above). Alternatively, when the STA support LDPC tone mapping based on one of the methods above, the capability information on the LDPC tone mapping may have the first value while, when the STA does not support the LDPC tone mapping, the capability information may have the second value.

In the S2810 step, the receiving apparatus (receiving STA) may receive the whole or part of an PPDU. The received signal may be in the form of FIG. 18.

Sub-steps of the S2810 step may be determined based on the S2730 step. In other words, the S2810 step may perform an operation of restoring the results of the CSD, spatial mapping, IDFT/IFFT, and GI insert operations applied in the S2730 step.

In the S2820 step, the receiving apparatus may perform decoding on the whole/part of the PPDU. Also, the receiving apparatus may obtain control information related to the tone plan (namely, RU) or sounding from the decoded PPDU.

More specifically, the receiving apparatus may decode the L-SIG and EHT-SIG of a PPDU based on the legacy STF/LTF and obtain information included in the L-SIG and EHT SIG fields. The information on various tone plans (namely, RUs) according to the present disclosure may be included in the EHT-SIG (EHT-SIG-A/B/C), and the receiving STA may obtain information on the tone plan (namely, RU) through the EHT-SIG.

In the S2830 step, the receiving apparatus may decode the remaining part of the PPDU based on the information on the tone plan (namely, RU) obtained through the S2820 step. For example, the receiving STA may decode the STF/LTF field of the PPDU based on the information on the tone plan (namely, RU). Also, the receiving STA may decode the data field of the PPDU based on the information on the tone plan (namely, the RU) and obtain the MPDU included in the data field.

Also, the receiving apparatus may perform a processing operation of transferring data decoded through the S2830 step to an upper layer (for example, MAC layer). Also, a subsequent operation may be performed when signal generation is instructed from the upper layer to the PHY layer in response to the data transferred to the upper layer.

The above-described PPDU may be received based on the device of FIG. 1.

As shown in FIG. 1, a receiving device may include a memory 122, a processor 121, and a transceiver 123.

The transceiver 123 may receive a PPDU based on the control of the processor 121. For example, the transceiver 123 may include multiple detailed units (not shown). For example, the transceiver 123 may include at least one receiving antenna and may include a filter for the corresponding receiving antenna.

The PPDU that is received through the transceiver 123 may be stored in the memory 122. The processor 121 may process decoding on the received PPDU through the memory 122. The processor 121 may obtain control information related to the tone-plan/RU included in the PPDU and may store the obtained control information in the memory 112.

The processor 121 may perform decoding on the received PPDU. More specifically, the processor 121 may perform operations of recovering (or reconfiguring) the results of the operations of CSD, Spatial Mapping, IDFT/IFFT operation, GI insertion, which are applied to the PPDU. The operations of recovering (or reconfiguring) the results of the operations of CSD, Spatial Mapping, IDFT/IFFT operation, GI insertion may be performed by multiple processing units (not shown) that are individually implemented in the processor 121.

Additionally, the processor 121 may decode a data field of the received PPDU through the transceiver 123.

Also, the processor 121 may process the decoded data. For example, the processor 121 may perform a processing operation of delivering (or transferring) information related to the decoded data field to a higher layer (e.g., MAC layer). Furthermore, when signal generation is instructed to the PHY layer from the higher layer in response to the data that is delivered to the higher layer, subsequent operations may be performed.

Hereinafter, the above-described embodiment will be described with reference to FIG. 1 to FIG. 28.

FIG. 29 is a flow diagram illustrating a procedure for a transmitting STA to transmit a PPDU according to the present embodiment.

One example of FIG. 29 may be performed in a network supporting the next-generation wireless LAN system (the IEEE 802.11be or EHT wireless LAN system). The next-generation wireless LAN system is an improved version of the 802.11ax system and may satisfy backward compatibility with the 802.11ax system.

The present embodiment proposes a method for performing LDPC tone mapping on a data bit string included in the data field of a PPDU when transmitting the PPDU by allocating a Multi-RU supported by the 802.11be wireless LAN system to one STA. The Multi-RU refers to an RU in which several consecutive or inconsecutive RUs are aggregated.

A transmitting STA may perform one example of FIG. 29, and the transmitting STA may correspond to an access point (AP). The receiving STA of FIG. 29 may correspond to an STA that supports an Extremely High Throughput (EHT) wireless LAN system.

In the S2910 step, a transmitting station (STA) generates a Physical Protocol Data Unit (PPDU) that includes a data field.

In the S2920 step, the transmitting STA transmits the PPDU to a receiving STA.

The data field is transmitted through a Multiple-Resource Unit (Multi-RU). Low Density Parity Check (LDPC) tone mapping is performed on the data tone included in the data field for the Multi-RU based on a first parameter.

The Multi-RU may be allocated to the receiving STA (one STA) in a combination of various RUs. Also, the first parameter may be determined according to the number of data tones in the Multi-RU. The first parameter may correspond to D_(TM), which is an LDPC tone mapping distance parameter. The D_(TM) may be a tone interval used in LDPC tone mapping.

For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is 18. When the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4. When the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is 6.

Low Density Parity Check (LDPC) tone mapping may be performed on the data tone included in the data field based on the first parameter. Specifically, the data field may be generated based on a bitstream. The bitstream may be mapped to the data tone based on constellation mapping. The tone spacing of the data tone may be set to the first parameter for the Multi-RU based on the LDPC tone mapping. The LDPC tone mapping is similar to the interleaving operation. The bitstream may be distributed at tone intervals of the first parameter to be mapped to data tones based on the LDPC tone mapping. Also, the bitstream may be modulated based on the constellation mapping before the LDPC tone mapping is performed.

Also, before the constellation mapping is performed, the bitstream may be divided into streams by the stream parser or divided for each frequency segment by the segment parser. The constellation mapping and the LDPC tone mapping may be performed for each stream and/or frequency segment. The stream and the frequency segment may be parsed according to a proportional ratio based on the round robin scheme. The variable S related to the proportional ratio may be defined as follows.

S=max(1,N _(BPSCS)/2)

In the equation above, N_(BPSCS) represents the number of coded bits per subcarrier per spatial stream. The coded bit may be determined by the Modulation and Coding Scheme (MCS) value.

When the transmitting STA supports a plurality of streams, the plurality of streams are divided into each stream by the stream parser, and the constellation mapping and the LDPC tone mapping may be performed for each stream.

If the Multi-RU is divided for each frequency segment by the segment parser, the constellation mapping and the LDPC tone mapping may be performed for each frequency segment. In this case, one frequency segment may correspond to each RU of the Multi-RU. That is, if the segment parser is used in the transmitting STA, the Multi-RU may be divided into each RU, and LDPC tone mapping may be performed separately for each RU. However, the present embodiment does not perform LDPC tone mapping separately for each RU but proposes a method of performing LDPC tone mapping by considering the Multi-RU to be one RU.

For each bitstream, 1) a PHY padding operation, 2) a scrambling operation, 3) an LDPC encoding operation, 4) a stream parsing operation that maps LDPC encoded bits to a specific spatial stream, and 5) a segment parsing operation that divides a Multi-RU into each frequency segment (each RU) may be performed (if required); and 6) the constellation mapping operation may be performed on the individual spatial streams and frequency segments, and 7) the LDPC tone mapping operation may be performed on the modulation symbols generated based on the constellation mapping. The transmitting STA performs the procedures 1) to 7) sequentially, and the present embodiment mainly describes the procedure 7).

In other words, the embodiment above describes an operation in which the LDPC tone mapping is performed on the Multi-RU, and the data tones are distributed at tone intervals of the first parameter. The index of the data tones may be determined as follows.

t(k)=D _(TM) (k mod N _(SD) /D _(TM))+floor(k*D _(TM) /N _(SD))

In the equation above, t(k) represents the index of the data tone, D_(TM) represents the first parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

A case in which the constellation mapping uses DCM may also be considered. When the Dual Carrier Modulation (DCM) is performed on the bitstream, the bitstream may be mapped to a first data tone based on the first constellation mapping and mapped to a second data tone based on the second constellation mapping.

The first to second constellation mapping may be one of Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), or 16-Quadrature Amplitude Modulation (QAM). However, when DCM is not applied, the constellation mapping may be one of the BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, or 1024-QAM.

The tone spacing for each of the first and second data tones may be set to the second parameter based on the LDPC tone mapping. The first and second data tones may be included in the data tone. For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the second parameter may be 13.

The second parameter may correspond to D_(TM_DCM), which is the LDPC tone mapping distance parameter when the DCM method is applied. The D_(TM_DCM) may be a tone spacing used for the LDPC tone mapping when DCM is applied.

When the DCM is applied, the first data tone may correspond to a lower half tone (or subcarrier k) on the frequency domain, and the second data tone may correspond to an upper half tone on the frequency domain (or subcarrier k+N/2). Here, the tone may be used interchangeably with the subcarrier.

The index of the first data tone may be determined as follows.

t(k)=D _(TM_DCM)(k mod N _(SD) /D _(TM_DCM))+floor(k*D _(TM_DCM) /N _(SD))

In the equation above, t(k) represents the index of the first data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

The index of the second data tone may be determined as follows.

t(k)=D _(TM_DCM)((k−N _(SD))mod N _(SD) /D _(TM_DCM))+floor((k−N _(SD))*D _(TM_DCM) /N _(SD))+N _(SD)

In the equation above, t(k) represents the index of the second data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

In one example, when the first and second constellation mapping use the BPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be generated by applying phase rotation to the first modulation symbol (d_(k+NSD)=d_(k)×e^(j(k+NSD)*pi)) The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In another example, when the first and second constellation mapping use the QPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be a complex conjugate of the first modulation symbol (d_(k+NSD)=conj(d_(k))). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In yet another example, when the first and second constellation mapping use the 16-QAM modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The bit order of a first bit group for the second modulation symbol may be different from the bit order of a second bit group for the first modulation symbol ((B_(4k), B_(4k+1), B_(4k+2), B_(4k+3))→(B_(4k+1)B_(4k), B_(4k+3), B_(4k+2))). The first and second bit groups may be included in the bitstream. The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

The 26 tone RU is a resource unit composed of 26 tones, and the 52 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 52 tone RU may be adjacent to each other or included within a 20 MHz channel.

The 26 tone RU is a resource unit composed of 26 tones, and the 106 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 106 tone RU may be adjacent to each other or included within a 20 MHz channel.

The PPDU may further include a control field. The control field may include a Universal-Signal (U-SIG) field and the EHT-SIG field. The control field may include allocation information for the Multi-RU, and the allocation information for the Multi-RU may include the size and location of the RU, control information related to the RU, information on the frequency domain that includes the RU, and information on an STA that receives the RU.

Also, the PPDU may include the Legacy-Signal (L-SIG) field, the Repeated Legacy-Signal (RL-SIG) field, the EHT-Short Training Field (STF), and the EHT-Long Training Field (LTF). The EHT-SIG field may include the EHT-SIG-A field and the EHT-SIG-B field. The EHT-SIG field may further include the EHT-SIG-C field.

FIG. 30 is a flow diagram illustrating a procedure for a receiving STA to receive a PPDU according to the present embodiment.

One example of FIG. 30 may be performed in a network supporting the next-generation wireless LAN system (the IEEE 802.11be or EHT wireless LAN system). The next-generation wireless LAN system is an improved version of the 802.11ax system and may satisfy backward compatibility with the 802.11ax system.

The present embodiment proposes a method for performing LDPC tone mapping on a data bit string included in the data field of a PPDU when transmitting the PPDU by allocating a Multi-RU supported by the 802.11be wireless LAN system to one STA. The Multi-RU refers to an RU in which several consecutive or inconsecutive RUs are aggregated.

A receiving STA may perform one example of FIG. 30, and the receiving STA may correspond to an STA that supports the Extremely High Throughput (EHT) wireless LAN system. The transmitting STA of FIG. 30 may correspond to an access point (AP).

In the S3010 step, the receiving STA receives a Physical Protocol Data Unit (PPDU) including a data field from a transmitting STA.

In the S3020 step, the receiving STA decodes the data field.

The data field is received through a Multiple-Resource Unit (Multi-RU). Low Density Parity Check (LDPC) tone mapping is performed on the data tone included in the data field for the Multi-RU based on a first parameter.

The Multi-RU may be allocated to the receiving STA (one STA) in a combination of various RUs. Also, the first parameter may be determined according to the number of data tones in the Multi-RU. The first parameter may correspond to D_(TM), which is an LDPC tone mapping distance parameter. The D_(TM) may be a tone interval used in LDPC tone mapping.

For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is 18. When the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4. When the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is 6.

Low Density Parity Check (LDPC) tone mapping may be performed on the data tone included in the data field based on the first parameter. Specifically, the data field may be generated based on a bitstream. The bitstream may be mapped to the data tone based on constellation mapping. The tone spacing of the data tone may be set to the first parameter for the Multi-RU based on the LDPC tone mapping. The LDPC tone mapping is similar to the interleaving operation. The bitstream may be distributed at tone intervals of the first parameter to be mapped to data tones based on the LDPC tone mapping. Also, the bitstream may be modulated based on the constellation mapping before the LDPC tone mapping is performed.

Also, before the constellation mapping is performed, the bitstream may be divided into streams by the stream parser or divided for each frequency segment by the segment parser. The constellation mapping and the LDPC tone mapping may be performed for each stream and/or frequency segment. The stream and the frequency segment may be parsed according to a proportional ratio based on the round robin scheme. The variable S related to the proportional ratio may be defined as follows.

S=max(1,N _(BPSCS)/2)

In the equation above, N_(BPSCS) represents the number of coded bits per subcarrier per spatial stream. The coded bit may be determined by the Modulation and Coding Scheme (MCS) value.

When the transmitting STA supports a plurality of streams, the plurality of streams are divided into each stream by the stream parser, and the constellation mapping and the LDPC tone mapping may be performed for each stream.

If the Multi-RU is divided for each frequency segment by the segment parser, the constellation mapping and the LDPC tone mapping may be performed for each frequency segment. In this case, one frequency segment may correspond to each RU of the Multi-RU. That is, if the segment parser is used in the transmitting STA, the Multi-RU may be divided into each RU, and LDPC tone mapping may be performed separately for each RU. However, the present embodiment does not perform LDPC tone mapping separately for each RU but proposes a method of performing LDPC tone mapping by considering the Multi-RU to be one RU.

For each bitstream, 1) a PHY padding operation, 2) a scrambling operation, 3) an LDPC encoding operation, 4) a stream parsing operation that maps LDPC encoded bits to a specific spatial stream, and 5) a segment parsing operation that divides a Multi-RU into each frequency segment (each RU) may be performed (if required); and 6) the constellation mapping operation may be performed on the individual spatial streams and frequency segments, and 7) the LDPC tone mapping operation may be performed on the modulation symbols generated based on the constellation mapping. The transmitting STA performs the procedures 1) to 7) sequentially, and the present embodiment mainly describes the procedure 7).

However, procedures 1) to 7) may be performed in reverse order as a receiving STA performs decoding of the data field. The STA which has received the data field from the transmitting apparatus may 8) perform LDPC tone demapping, 9) may obtain the bit string again from modulation symbols by performing constellation demapping, 10) may not map the bit string for each spatial stream or frequency segment through the stream deparser or segment deparser, 11) may perform LDPC decoding, 12) may perform a descrambling operation, and 13) may perform Pre-FEC padding or Post-FEC padding. The receiving STA may decode the bitstream (input bitstream) through the procedures 8) to 13).

In other words, the embodiment above describes an operation in which the LDPC tone mapping is performed on the Multi-RU, and the data tones are distributed at tone intervals of the first parameter. The index of the data tones may be determined as follows.

t(k)=D _(TM)(k mod N _(SD) /D _(TM))+floor(k*D _(TM) /N _(SD))

In the equation above, t(k) represents the index of the data tone, D_(TM) represents the first parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

A case in which the constellation mapping uses DCM may also be considered. When the Dual Carrier Modulation (DCM) is performed on the bitstream, the bitstream may be mapped to a first data tone based on the first constellation mapping and mapped to a second data tone based on the second constellation mapping.

The first to second constellation mapping may be one of Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), or 16-Quadrature Amplitude Modulation (QAM). However, when DCM is not applied, the constellation mapping may be one of the BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, or 1024-QAM.

The tone spacing for each of the first and second data tones may be set to the second parameter based on the LDPC tone mapping. The first and second data tones may be included in the data tone. For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the second parameter may be 13.

The second parameter may correspond to D_(TM_DCM), which is the LDPC tone mapping distance parameter when the DCM method is applied. The D_(TM_DCM) may be a tone spacing used for the LDPC tone mapping when DCM is applied.

When the DCM is applied, the first data tone may correspond to a lower half tone (or subcarrier k) on the frequency domain, and the second data tone may correspond to an upper half tone on the frequency domain (or subcarrier k+N/2). Here, the tone may be used interchangeably with the subcarrier.

The index of the first data tone may be determined as follows.

t(k)=D _(TM_DCM)(k mod N _(SD) /D _(TM_DCM))+floor(k*D _(TM_DCM) /N _(SD))

In the equation above, t(k) represents the index of the first data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

The index of the second data tone may be determined as follows.

t(k)=D _(TM_DCM)((k−N _(SD))mod N _(SD) /D _(TM_DCM))+floor((k−N _(SD))*D _(TM_DCM) /N _(SD))N _(SD)

In the equation above, t(k) represents the index of the second data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

In one example, when the first and second constellation mapping use the BPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be generated by applying phase rotation to the first modulation symbol (d_(k+NSD)=d_(k)×e^(j(k+NSD)*pi)). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In another example, when the first and second constellation mapping use the QPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be a complex conjugate of the first modulation symbol (d_(k+NSD)=conj(d_(k))). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In yet another example, when the first and second constellation mapping use the 16-QAM modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The bit order of a first bit group for the second modulation symbol may be different from the bit order of a second bit group for the first modulation symbol ((B_(4k), B_(4k+1), B_(4k+2), B_(4k+3))→(B_(4k+1), B_(4k), B_(4k+3), B_(4k+2))). The first and second bit groups may be included in the bitstream. The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

The 26 tone RU is a resource unit composed of 26 tones, and the 52 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 52 tone RU may be adjacent to each other or included within a 20 MHz channel.

The 26 tone RU is a resource unit composed of 26 tones, and the 106 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 106 tone RU may be adjacent to each other or included within a 20 MHz channel.

The PPDU may further include a control field. The control field may include a Universal-Signal (U-SIG) field and the EHT-SIG field. The control field may include allocation information for the Multi-RU, and the allocation information for the Multi-RU may include the size and location of the RU, control information related to the RU, information on the frequency domain that includes the RU, and information on an STA that receives the RU.

Also, the PPDU may include the Legacy-Signal (L-SIG) field, the Repeated Legacy-Signal (RL-SIG) field, the EHT-Short Training Field (STF), and the EHT-Long Training Field (LTF). The EHT-SIG field may include the EHT-SIG-A field and the EHT-SIG-B field. The EHT-SIG field may further include the EHT-SIG-C field.

5. Device Configuration

FIG. 31 illustrates an example of a modified transmitting device and/or receiving device of the present specification.

Each device/STA shown in sub-figures (a)/(b) of FIG. 1 may be modified as shown in FIG. 31. A transceiver 630 of FIG. 31 may be the same as the transceiver(s) 113 and 123 of FIG. 1. The transceiver 630 of FIG. 31 may include a receiver and a transmitter.

A processor 610 of FIG. 31 may be the same as the processor(s) 111 and 121 shown in FIG. 1. Alternatively, the processor 610 of FIG. 31 may be the same as the processing chip(s) 114 and 124 shown in FIG. 1.

A memory 150 of FIG. 31 may be the same as the memory(s) 112 and 122 shown in FIG. 1. Alternatively, the memory 150 of FIG. 31 may be a separate external memory that is different from the memory(s) 112 and 122 shown in FIG. 1.

Referring to FIG. 31, the power management module 611 manages power for the processor 610 and/or the transceiver 630. The battery 612 supplies power to the power management module 611. The display 613 outputs results processed by the processor 610. The keypad 614 receives inputs that are to be used by the processor 610. The keypad 614 may be shown on the display 613. The SIM card 615 may be an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices, such as mobile phones and computers.

Referring to FIG. 31, the speaker 640 may output sound-related results processed by the processor 610. The microphone 641 may receive sound-related inputs to be used by the processor 610.

The technical features of the present disclosure may be applied to various devices and methods. For example, the technical features of the present disclosure may be performed/supported through the devices of FIG. 1 and/or FIG. 31. For example, the technical features of the present disclosure may be applied to only part of FIG. 1 and/or FIG. 31. For example, the technical features of the present disclosure may be implemented based on the processing chip(s) 114, 124 of FIG. 1, or implemented based on the processor(s) 111, 121 and the memory(s) 112, 122, or implemented based on the processor 610 and the memory 620 of FIG. 31. For example, the apparatus according to the present disclosure receives a Physical Protocol Data Unit (PPDU) that includes a data field from a transmitting STA and decodes the data field.

The data field is received through a Multiple-Resource Unit (Multi-RU). Low Density Parity Check (LDPC) tone mapping is performed on the data tone included in the data field for the Multi-RU based on a first parameter.

The Multi-RU may be allocated to the receiving STA (one STA) in a combination of various RUs. Also, the first parameter may be determined according to the number of data tones in the Multi-RU. The first parameter may correspond to D_(TM), which is an LDPC tone mapping distance parameter. The D_(TM) may be a tone interval used in LDPC tone mapping.

For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is 18. When the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4. When the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is 6.

Low Density Parity Check (LDPC) tone mapping may be performed on the data tone included in the data field based on the first parameter. Specifically, the data field may be generated based on a bitstream. The bitstream may be mapped to the data tone based on constellation mapping. The tone spacing of the data tone may be set to the first parameter for the Multi-RU based on the LDPC tone mapping. The LDPC tone mapping is similar to the interleaving operation. The bitstream may be distributed at tone intervals of the first parameter to be mapped to data tones based on the LDPC tone mapping. Also, the bitstream may be modulated based on the constellation mapping before the LDPC tone mapping is performed.

Also, before the constellation mapping is performed, the bitstream may be divided into streams by the stream parser or divided for each frequency segment by the segment parser. The constellation mapping and the LDPC tone mapping may be performed for each stream and/or frequency segment. The stream and the frequency segment may be parsed according to a proportional ratio based on the round robin scheme. The variable S related to the proportional ratio may be defined as follows.

S=max(1,N _(BPSCS)/2)

In the equation above, N_(BPSCS) represents the number of coded bits per subcarrier per spatial stream. The coded bit may be determined by the Modulation and Coding Scheme (MCS) value.

When the transmitting STA supports a plurality of streams, the plurality of streams are divided into each stream by the stream parser, and the constellation mapping and the LDPC tone mapping may be performed for each stream.

If the Multi-RU is divided for each frequency segment by the segment parser, the constellation mapping and the LDPC tone mapping may be performed for each frequency segment. In this case, one frequency segment may correspond to each RU of the Multi-RU. That is, if the segment parser is used in the transmitting STA, the Multi-RU may be divided into each RU, and LDPC tone mapping may be performed separately for each RU. However, the present embodiment does not perform LDPC tone mapping separately for each RU but proposes a method of performing LDPC tone mapping by considering the Multi-RU to be one RU.

For each bitstream, 1) a PHY padding operation, 2) a scrambling operation, 3) an LDPC encoding operation, 4) a stream parsing operation that maps LDPC encoded bits to a specific spatial stream, and 5) a segment parsing operation that divides a Multi-RU into each frequency segment (each RU) may be performed (if required); and 6) the constellation mapping operation may be performed on the individual spatial streams and frequency segments, and 7) the LDPC tone mapping operation may be performed on the modulation symbols generated based on the constellation mapping. The transmitting STA performs the procedures 1) to 7) sequentially, and the present embodiment mainly describes the procedure 7).

In other words, the embodiment above describes an operation in which the LDPC tone mapping is performed on the Multi-RU, and the data tones are distributed at tone intervals of the first parameter. The index of the data tones may be determined as follows.

t(k)=D _(TM)(k mod N _(SD) /D _(TM))+floor(k*D _(TM) /N _(SD))

In the equation above, t(k) represents the index of the data tone, D_(TM) represents the first parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

A case in which the constellation mapping uses DCM may also be considered. When the Dual Carrier Modulation (DCM) is performed on the bitstream, the bitstream may be mapped to a first data tone based on the first constellation mapping and mapped to a second data tone based on the second constellation mapping.

The first to second constellation mapping may be one of Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), or 16-Quadrature Amplitude Modulation (QAM). However, when DCM is not applied, the constellation mapping may be one of the BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, or 1024-QAM.

The tone spacing for each of the first and second data tones is set to the second parameter based on the LDPC tone mapping. The first and second data tones may be included in the data tone. For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the second parameter may be 13.

The second parameter may correspond to D_(TM_DCM), which is the LDPC tone mapping distance parameter when the DCM method is applied. The D_(TM_DCM) may be a tone spacing used for the LDPC tone mapping when DCM is applied.

When the DCM is applied, the first data tone may correspond to a lower half tone (or subcarrier k) on the frequency domain, and the second data tone may correspond to an upper half tone on the frequency domain (or subcarrier k+N/2). Here, the tone may be used interchangeably with the subcarrier.

The index of the first data tone may be determined as follows.

t(k)=D _(TM_DCM)(k mod N _(SD) /D _(TM_DCM))+floor(k*D _(TM_DCM) /N _(SD))

In the equation above, t(k) represents the index of the first data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

The index of the second data tone may be determined as follows.

t(k)=D _(TM_DCM)((k−N _(SD))mod N _(SD) /D _(TM_DCM))floor((k−N _(SD))*D _(TM_DCM) /N _(SD))+N _(SD)

In the equation above, t(k) represents the index of the second data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

In one example, when the first and second constellation mapping use the BPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be generated by applying phase rotation to the first modulation symbol (d_(k+NSD)=d_(k)×e^(j(k+NSD)*pi)). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In another example, when the first and second constellation mapping use the QPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be a complex conjugate of the first modulation symbol (d_(k+NSD)=conj(d_(k))). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In yet another example, when the first and second constellation mapping use the 16-QAM modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The bit order of a first bit group for the second modulation symbol may be different from the bit order of a second bit group for the first modulation symbol ((B_(4k), B_(4k+1), B_(4k+2), B_(4k+3))→(B_(4k+1), B_(4k), B_(4k+3), B_(4k+2))). The first and second bit groups may be included in the bitstream. The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

The 26 tone RU is a resource unit composed of 26 tones, and the 52 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 52 tone RU may be adjacent to each other or included within a 20 MHz channel.

The 26 tone RU is a resource unit composed of 26 tones, and the 106 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 106 tone RU may be adjacent to each other or included within a 20 MHz channel.

The PPDU may further include a control field. The control field may include a Universal-Signal (U-SIG) field and the EHT-SIG field. The control field may include allocation information for the Multi-RU, and the allocation information for the Multi-RU may include the size and location of the RU, control information related to the RU, information on the frequency domain that includes the RU, and information on an STA that receives the RU.

Also, the PPDU may include the Legacy-Signal (L-SIG) field, the Repeated Legacy-Signal (RL-SIG) field, the EHT-Short Training Field (STF), and the EHT-Long Training Field (LTF). The EHT-SIG field may include the EHT-SIG-A field and the EHT-SIG-B field. The EHT-SIG field may further include the EHT-SIG-C field.

The technical features of the present disclosure may be implemented based on a computer readable medium (CRM). For example, a CRM according to the present disclosure is at least one computer readable medium including instructions designed to be executed by at least one processor.

The CRM may store instructions that perform operations including receiving a Physical Protocol Data Unit (PPDU) from a transmitting STA through a broadband and decoding the PPDU. At least one processor may execute the instructions stored in the CRM according to the present disclosure. At least one processor related to the CRM of the present disclosure may be the processor 111, 121 of FIG. 1, the processing chip 114, 124 of FIG. 1, or the processor 610 of FIG. 31. Meanwhile, the CRM of the present disclosure may be the memory 112, 122 of FIG. 1, the memory 620 of FIG. 31, or a separate external memory/storage medium/disk.

The data field is received through a Multiple-Resource Unit (Multi-RU). Low Density Parity Check (LDPC) tone mapping is performed on the data tone included in the data field for the Multi-RU based on a first parameter.

The Multi-RU may be allocated to the receiving STA (one STA) in a combination of various RUs. Also, the first parameter may be determined according to the number of data tones in the Multi-RU. The first parameter may correspond to D_(TM), which is an LDPC tone mapping distance parameter. The D_(TM) may be a tone interval used in LDPC tone mapping.

For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is 18. When the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4. When the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is 6.

Low Density Parity Check (LDPC) tone mapping may be performed on the data tone included in the data field based on the first parameter. Specifically, the data field may be generated based on a bitstream. The bitstream may be mapped to the data tone based on constellation mapping. The tone spacing of the data tone may be set to the first parameter for the Multi-RU based on the LDPC tone mapping. The LDPC tone mapping is similar to the interleaving operation. The bitstream may be distributed at tone intervals of the first parameter to be mapped to data tones based on the LDPC tone mapping. Also, the bitstream may be modulated based on the constellation mapping before the LDPC tone mapping is performed.

Also, before the constellation mapping is performed, the bitstream may be divided into streams by the stream parser or divided for each frequency segment by the segment parser. The constellation mapping and the LDPC tone mapping may be performed for each stream and/or frequency segment. The stream and the frequency segment may be parsed according to a proportional ratio based on the round robin scheme. The variable S related to the proportional ratio may be defined as follows.

S=max(1,N _(BPSCS)/2)

In the equation above, N_(BPSCS) represents the number of coded bits per subcarrier per spatial stream. The coded bit may be determined by the Modulation and Coding Scheme (MCS) value.

When the transmitting STA supports a plurality of streams, the plurality of streams are divided into each stream by the stream parser, and the constellation mapping and the LDPC tone mapping may be performed for each stream.

If the Multi-RU is divided for each frequency segment by the segment parser, the constellation mapping and the LDPC tone mapping may be performed for each frequency segment. In this case, one frequency segment may correspond to each RU of the Multi-RU. That is, if the segment parser is used in the transmitting STA, the Multi-RU may be divided into each RU, and LDPC tone mapping may be performed separately for each RU. However, the present embodiment does not perform LDPC tone mapping separately for each RU but proposes a method of performing LDPC tone mapping by considering the Multi-RU to be one RU.

For each bitstream, 1) a PHY padding operation, 2) a scrambling operation, 3) an LDPC encoding operation, 4) a stream parsing operation that maps LDPC encoded bits to a specific spatial stream, and 5) a segment parsing operation that divides a Multi-RU into each frequency segment (each RU) may be performed (if required); and 6) the constellation mapping operation may be performed on the individual spatial streams and frequency segments, and 7) the LDPC tone mapping operation may be performed on the modulation symbols generated based on the constellation mapping. The transmitting STA performs the procedures 1) to 7) sequentially, and the present embodiment mainly describes the procedure 7).

In other words, the embodiment above describes an operation in which the LDPC tone mapping is performed on the Multi-RU, and the data tones are distributed at tone intervals of the first parameter. The index of the data tones may be determined as follows.

t(k)=D _(TM)(k mod N _(SD) /D _(TM))+floor(k*D _(TM) /N _(SD))

In the equation above, t(k) represents the index of the data tone, D_(TM) represents the first parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

A case in which the constellation mapping uses DCM may also be considered. When the Dual Carrier Modulation (DCM) is performed on the bitstream, the bitstream may be mapped to a first data tone based on the first constellation mapping and mapped to a second data tone based on the second constellation mapping.

The first to second constellation mapping may be one of Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), or 16-Quadrature Amplitude Modulation (QAM). However, when DCM is not applied, the constellation mapping may be one of the BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, or 1024-QAM.

The tone spacing for each of the first and second data tones may be set to the second parameter based on the LDPC tone mapping. The first and second data tones may be included in the data tone. For example, when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the second parameter may be 13.

The second parameter may correspond to D_(TM_DCM), which is the LDPC tone mapping distance parameter when the DCM method is applied. The D_(TM_DCM) may be a tone spacing used for the LDPC tone mapping when DCM is applied.

When the DCM is applied, the first data tone may correspond to a lower half tone (or subcarrier k) on the frequency domain, and the second data tone may correspond to an upper half tone on the frequency domain (or subcarrier k+N/2). Here, the tone may be used interchangeably with the subcarrier.

The index of the first data tone may be determined as follows.

t(k)=D _(TM_DCM)(k mod N _(SD) /D _(TM_DCM))+floor(k*D _(TM_DCM) /N _(SD))

In the equation above, t(k) represents the index of the first data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

The index of the second data tone may be determined as follows.

t(k)=D _(TM_DCM)((k−N _(SD))mod N _(SD) /D _(TM_DCM))+floor((k−N _(SD))*D _(TM_DCM) /N _(SD))+N _(SD)

In the equation above, t(k) represents the index of the second data tone, D_(TM_DCM) represents the second parameter, k represents the index of the tone to which the bitstream has been mapped, N_(SD) represents the number of data tones in the Multi-RU, and floor represents a rounding-down function.

In one example, when the first and second constellation mapping use the BPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be generated by applying phase rotation to the first modulation symbol (d_(k+NSD)=d_(k)×e^(j(k+NSD)*pi)) The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In another example, when the first and second constellation mapping use the QPSK modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The second modulation symbol may be a complex conjugate of the first modulation symbol (d_(k+NSD)=conj(d_(k))). The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

In yet another example, when the first and second constellation mapping use the 16-QAM modulation method, the bitstream may be modulated to a first modulation symbol based on the first constellation mapping and a second modulation symbol based on the second constellation mapping. The bit order of a first bit group for the second modulation symbol may be different from the bit order of a second bit group for the first modulation symbol ((B_(4k), B_(4k+1), B_(4k+2), B_(4k+3))→(B_(4k+1), B_(4k), B_(4k+3), B_(4k+2))). The first and second bit groups may be included in the bitstream. The first modulation symbol may be mapped to the first data tone, and the second modulation symbol may be mapped to the second data tone.

The 26 tone RU is a resource unit composed of 26 tones, and the 52 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 52 tone RU may be adjacent to each other or included within a 20 MHz channel.

The 26 tone RU is a resource unit composed of 26 tones, and the 106 tone RU is a resource unit composed of 52 tones. The 26 tone RU and the 106 tone RU may be adjacent to each other or included within a 20 MHz channel.

The PPDU may further include a control field. The control field may include a Universal-Signal (U-SIG) field and the EHT-SIG field. The control field may include allocation information for the Multi-RU, and the allocation information for the Multi-RU may include the size and location of the RU, control information related to the RU, information on the frequency domain that includes the RU, and information on an STA that receives the RU.

Also, the PPDU may include the Legacy-Signal (L-SIG) field, the Repeated Legacy-Signal (RL-SIG) field, the EHT-Short Training Field (STF), and the EHT-Long Training Field (LTF). The EHT-SIG field may include the EHT-SIG-A field and the EHT-SIG-B field. The EHT-SIG field may further include the EHT-SIG-C field.

The foregoing technical features of the present specification are applicable to various applications or business models. For example, the foregoing technical features may be applied for wireless communication of a device supporting artificial intelligence (AI).

Artificial intelligence refers to a field of study on artificial intelligence or methodologies for creating artificial intelligence, and machine learning refers to a field of study on methodologies for defining and solving various issues in the area of artificial intelligence. Machine learning is also defined as an algorithm for improving the performance of an operation through steady experiences of the operation.

An artificial neural network (ANN) is a model used in machine learning and may refer to an overall problem-solving model that includes artificial neurons (nodes) forming a network by combining synapses. The artificial neural network may be defined by a pattern of connection between neurons of different layers, a learning process of updating a model parameter, and an activation function generating an output value.

The artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses that connect neurons. In the artificial neural network, each neuron may output a function value of an activation function of input signals input through a synapse, weights, and deviations.

A model parameter refers to a parameter determined through learning and includes a weight of synapse connection and a deviation of a neuron. A hyper-parameter refers to a parameter to be set before learning in a machine learning algorithm and includes a learning rate, the number of iterations, a mini-batch size, and an initialization function.

Learning an artificial neural network may be intended to determine a model parameter for minimizing a loss function. The loss function may be used as an index for determining an optimal model parameter in a process of learning the artificial neural network.

Machine learning may be classified into supervised learning, unsupervised learning, and reinforcement learning.

Supervised learning refers to a method of training an artificial neural network with a label given for training data, wherein the label may indicate a correct answer (or result value) that the artificial neural network needs to infer when the training data is input to the artificial neural network. Unsupervised learning may refer to a method of training an artificial neural network without a label given for training data. Reinforcement learning may refer to a training method for training an agent defined in an environment to choose an action or a sequence of actions to maximize a cumulative reward in each state.

Machine learning implemented with a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks is referred to as deep learning, and deep learning is part of machine learning. Hereinafter, machine learning is construed as including deep learning.

The foregoing technical features may be applied to wireless communication of a robot.

Robots may refer to machinery that automatically process or operate a given task with own ability thereof. In particular, a robot having a function of recognizing an environment and autonomously making a judgment to perform an operation may be referred to as an intelligent robot.

Robots may be classified into industrial, medical, household, military robots and the like according uses or fields. A robot may include an actuator or a driver including a motor to perform various physical operations, such as moving a robot joint. In addition, a movable robot may include a wheel, a brake, a propeller, and the like in a driver to run on the ground or fly in the air through the driver.

The foregoing technical features may be applied to a device supporting extended reality.

Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphic technology of providing a real-world object and background only in a CG image, AR technology is a computer graphic technology of providing a virtual CG image on a real object image, and MR technology is a computer graphic technology of providing virtual objects mixed and combined with the real world.

MR technology is similar to AR technology in that a real object and a virtual object are displayed together. However, a virtual object is used as a supplement to a real object in AR technology, whereas a virtual object and a real object are used as equal statuses in MR technology.

XR technology may be applied to a head-mount display (HMD), a head-up display (HUD), a mobile phone, a tablet PC, a laptop computer, a desktop computer, a TV, digital signage, and the like. A device to which XR technology is applied may be referred to as an XR device.

The claims recited in the present specification may be combined in a variety of ways. For example, the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method. In addition, the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method. 

1. A method in a wireless LAN system, the method comprising: receiving a Physical Protocol Data Unit (PPDU) including a data field by a receiving station (STA) from a transmitting STA; and decoding the data field by the receiving STA, wherein the data field is received through a Multiple-Resource Unit (Multi-RU), Low Density Parity Check (LDPC) tone mapping is performed on a data tone included in the data field based on a first parameter for the Multi-RU, and when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is
 18. 2. The method of claim 1, wherein, when the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4, and when the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is
 6. 3. The method of claim 2, wherein the data field is generated based on a bitstream, the bitstream is mapped to the data tone based on constellation mapping, and tone spacing of the data tone is set to the first parameter for the Multi-RU based on the LDPC tone mapping.
 4. The method of claim 3, wherein the index of the data tone is determined as t(k)=D_(TM) (k mod N_(SD)/D_(TM))+floor(k*D_(TM)/N_(SD)), where t(k) is the index of the data tone, D_(TM) is the first parameter, k is the index of a tone to which the bitstream has been mapped, N_(SD) is the number of data tones in the Multi-RU, and floor is a rounding-down function.
 5. The method of claim 4, wherein, when Dual Carrier Modulation (DCM) is performed on the bitstream, the bitstream is mapped to a first data tone based on first constellation mapping and mapped to a second data tone based on second constellation mapping, tone spacing for each of the first and second data tones is set to the second parameter for the Multi-RU based on the LDPC tone mapping, the first and second data tones are included in the data tone, and when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the second parameter is
 13. 6. The method of claim 5, wherein the first data tone is a lower half tone on the frequency domain, and the second data tone is an upper half tone on the frequency domain.
 7. The method of claim 6, wherein the index of the first data tone is determined as t(k)=D_(TM_DCM)(k mod N_(SD)/D_(TM_DCM))+floor(k*D_(TM_DCM)/N_(SD)), where t(k) is the index of the first data tone, D_(TM_DCM) is the second parameter, k is the index of a tone to which the bitstream has been mapped, N_(SD) is the number of data tones in the Multi-RU, and floor is a rounding-down function.
 8. The method of claim 6, wherein the index of the second data tone is determined as t(k)=D _(TM_DCM)(k−N _(SD))mod N _(SD) /D _(TM_DCM))+floor(k−N _(SD))*D _(TM_DCM) /N _(SD))+N _(SD), where t(k) is the index of the second data tone, D_(TM_DCM) is the second parameter, k is the index of a tone to which the bitstream has been mapped, N_(SD) is the number of data tones in the Multi-RU, and floor is a rounding-down function.
 9. The method of claim 2, wherein the 26 tone RU is a resource unit composed of 26 tones, the 52 tone RU is a resource unit composed of 52 tones, and the 26 tone RU and the 52 tone RU are adjacent to each other or included within a 20 MHz channel.
 10. The method of claim 2, wherein the 26 tone RU is a resource unit composed of 26 tones, the 106 tone RU is a resource unit composed of 106 tones, and the 26 tone RU and the 106 tone RU are adjacent to each other or included within a 20 MHz channel.
 11. The method of claim 1, wherein the PPDU further includes a control field, and the control field includes allocation information on the Multi-RU.
 12. A receiving station (STA) in a wireless LAN system, the receiving STA comprising: a memory; a transceiver; and a processor combined operatively with the memory and the transceiver, wherein the processor is configured to: receive a Physical Protocol Data Unit (PPDU) including a data field from a transmitting STA; and decode the data field, wherein the data field is received through a Multiple-Resource Unit (Multi-RU), Low Density Parity Check (LDPC) tone mapping is performed on a data tone included in the data field based on a first parameter for the Multi-RU, and when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is
 18. 13. A method in a wireless LAN system, the method comprising: generating a Physical Protocol Data Unit (PPDU) including a data field by a transmitting station (STA); and transmitting the PPDU to a receiving STA by the transmitting STA, wherein the data field is transmitted through a Multiple-Resource Unit (Multi-RU), Low Density Parity Check (LDPC) tone mapping is performed on a data tone included in the data field based on a first parameter for the Multi-RU, and when the Multi-RU is an RU in which a 242 tone RU and a 484 tone RU are aggregated, the first parameter is
 18. 14. The method of claim 13, wherein, when the Multi-RU is an RU in which a 26 tone RU and a 52 tone RU are aggregated, the first parameter is 4, and when the Multi-RU is an RU in which a 26 tone RU and a 106 tone RU are aggregated, the first parameter is
 6. 15. The method of claim 14, wherein the data field is generated based on a bitstream, the bitstream is mapped to the data tone based on constellation mapping, and tone spacing of the data tone is set to the first parameter for the Multi-RU based on the LDPC tone mapping. 16-19. (canceled) 